Underwater user interface

ABSTRACT

The present disclosure generally relates to underwater user interfaces. In some embodiments, a method includes at an electronic device with a display and one or more input devices, receiving a first request to display a user interface for accessing a first function of the electronic device. In response to receiving the first request, and in accordance with a determination that the electronic device is under water, the method includes displaying a first user interface for accessing the first function. In response to receiving the first request, and in accordance with a determination that the electronic device is not under water, the method also includes displaying a second user interface for accessing the first function.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.16/222,619 (now U.S. Publication No. 2020-0104021), filed Dec. 17, 2018,which claims benefit of U.S. Provisional Patent Application No.62/738,832, entitled “UNDERWATER USER INTERFACE,” filed on Sep. 28,2018, which are hereby incorporated by reference in their entirety forall purposes.

FIELD

The present disclosure relates generally to computer user interfaces,and more specifically to techniques for accessing underwater userinterfaces and for operating an electronic device while the electronicdevice is under water.

BACKGROUND

As electronic devices are manufactured to be water resistant or waterproof, some users are using their electronic devices while engaging inwater based activities or other activities that cause their electronicdevices to come in contact with water or other liquids. Users will, insome circumstances, operate their electronic devices while theelectronic devices are wet.

Exemplary user interface hierarchies include groups of related userinterfaces used for: organizing files and applications; storing and/ordisplaying digital images, editable documents (e.g., word processing,spreadsheet, and presentation documents), and/or non-editable documents(e.g., secured files and/or .pdf documents); recording and/or playingvideo and/or music; text-based communication (e.g., e-mail, texts,tweets, and social networking); voice and/or video communication (e.g.,phone calls and video conferencing); and web browsing. A user will, insome circumstances, need to perform such user interface navigationswithin or between a file management program (e.g., Finder from AppleInc. of Cupertino, Calif.), an image management application (e.g.,Photos from Apple Inc. of Cupertino, Calif.), a digital content (e.g.,videos and music) management application (e.g., iTunes from Apple Inc.of Cupertino, Calif.), a drawing application, a presentation application(e.g., Keynote from Apple Inc. of Cupertino, Calif.), a word processingapplication (e.g., Pages from Apple Inc. of Cupertino, Calif.), or aspreadsheet application (e.g., Numbers from Apple Inc. of Cupertino,Calif.).

But methods for performing these navigations and animating thetransition between related user interfaces in a user interface hierarchyare cumbersome and inefficient. In addition, these methods take longerthan necessary, thereby wasting energy. This latter consideration isparticularly important in battery-operated devices.

Additionally, abrupt transitions between different user interfaces canbe distracting and jarring for users, reducing the efficiency andenjoyment of the user when using the device.

It is well understood that the use of personally identifiableinformation should follow privacy policies and practices that aregenerally recognized as meeting or exceeding industry or governmentalrequirements for maintaining the privacy of users. In particular,personally identifiable information data should be managed and handledso as to minimize risks of unintentional or unauthorized access or use,and the nature of authorized use should be clearly indicated to users.

BRIEF SUMMARY

Current methods for displaying user interfaces while an electronicdevice is under water are outdated, time consuming, and inefficient. Forexample, some existing methods use complex and time-consuming userinterfaces, which may include multiple key presses or keystrokes, andmay include extraneous user interfaces. In addition, these methods takelonger than necessary, thereby wasting energy. This latter considerationis particularly important in battery-operated devices.

Accordingly, the present technique provides electronic devices withfaster, more efficient methods for accessing underwater user interfacesand interfaces for interacting with an electronic device while theelectronic device is under water. Such methods and interfaces optionallycomplement or replace other methods and interfaces for interacting withan electronic device while the electronic device is under water. Suchmethods and interfaces reduce the number, extent, and/or nature of theinputs from a user, reduce the cognitive burden on the user, and producea more efficient human-machine interface. For battery-operated computingdevices, such methods and interfaces conserve power and increase thetime between battery charges. Further, such methods and interfaces alsostreamline operations performed to access underwater user interfaces andfor operating an electronic device while underwater, which reduceunnecessary received inputs and improves user efficiency and output.

The above deficiencies and other problems associated with userinterfaces for electronic devices (e.g., with touch-sensitive surfaces)are reduced or eliminated by the disclosed devices. In some embodiments,the device is a desktop computer. In some embodiments, the device isportable (e.g., a notebook computer, tablet computer, or handhelddevice). In some embodiments, the device is a personal electronic device(e.g., a wearable electronic device, such as a watch). In someembodiments, the device has a touchpad. In some embodiments, the devicehas a touch-sensitive display (also known as a “touch screen” or“touch-screen display”). In some embodiments, the device has a graphicaluser interface (GUI), one or more processors, memory and one or moremodules, programs or sets of instructions stored in the memory forperforming multiple functions. In some embodiments, the user interactswith the GUI primarily through stylus and/or finger contacts andgestures on the touch-sensitive surface. In some embodiments, thefunctions optionally include image editing, drawing, presenting, wordprocessing, spreadsheet making, game playing, telephoning, videoconferencing, e-mailing, instant messaging, workout support, digitalphotographing, digital videoing, web browsing, digital music playing,note taking, and/or digital video playing. Executable instructions forperforming these functions are, optionally, included in a non-transitorycomputer readable storage medium or other computer program productconfigured for execution by one or more processors.

In accordance with some embodiments, a method is performed at anelectronic device with a display and one or more input devices. Themethod includes receiving a first request to display a user interfacefor accessing a first function of the electronic device. In response toreceiving the first request, and in accordance with a determination thatthe electronic device is underwater, the method includes displaying afirst user interface for accessing the first function. In response toreceiving the first request, and in accordance with a determination thatthe electronic device is not underwater, the method includes displayinga second user interface for accessing the first function.

In accordance with some embodiments, a non-transitory computer-readablestorage medium comprising one or more programs, the one or more programsincluding instructions which, when executed by an electronic device witha display and one or more input devices, causes the electronic device toreceive a first request to display a user interface for accessing afirst function of the electronic device. In response to receiving thefirst request, and in accordance with a determination that theelectronic device is underwater, the instructions also cause theelectronic device to display a first user interface for accessing thefirst function. In response to receiving the first request, and inaccordance with a determination that the electronic device is notunderwater, the instructions also cause the electronic device to displaya second user interface for accessing the first function.

In accordance with some embodiments, an electronic device includes adisplay, one or more input devices, one or more processors, memory, andone or more programs; the one or more programs are stored in the memoryand configured to be executed by the one or more processors, and the oneor more programs include instructions for performing or causingperformance of the operations of any of the methods described herein. Inaccordance with some embodiments, a non-transitory computer readablestorage medium has stored therein one or more programs, the one or moreprograms including instructions which, when executed by one or moreprocessors of an electronic device with a display and one or more inputdevices, cause the electronic device to perform or cause performance ofthe operations of any of the methods described herein. In accordancewith some embodiments, a graphical user interface on an electronicdevice with a display and one or more input devices, memory, and one ormore processors to execute one or more programs stored in the memoryincludes one or more of the elements displayed in any of the methodsdescribed herein, which are updated in response to inputs, as describedin any of the methods described herein. In accordance with someembodiments, an electronic device includes: a display, one or more inputdevices, and means for performing or causing performance of theoperations of any of the methods described herein. In accordance withsome embodiments, an information processing apparatus, for use in anelectronic device with a display and one or more input devices, includesmeans for performing or causing performance of the operations of any ofthe methods described herein.

Executable instructions for performing these functions are, optionally,included in a non-transitory computer-readable storage medium or othercomputer program product configured for execution by one or moreprocessors. Executable instructions for performing these functions are,optionally, included in a transitory computer-readable storage medium orother computer program product configured for execution by one or moreprocessors.

Thus, devices are provided with faster, more efficient methods foraccessing underwater user interfaces and interfaces for interacting withan electronic device while the electronic device is under water, therebyincreasing the effectiveness, efficiency, and user satisfaction withsuch devices. Such methods and interfaces may complement or replaceother methods for accessing underwater user interfaces.

DESCRIPTION OF THE FIGURES

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 4B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIG. 5A illustrates a personal electronic device in accordance with someembodiments.

FIG. 5B is a block diagram illustrating a personal electronic device inaccordance with some embodiments.

FIGS. 5C-5D illustrate exemplary components of a personal electronicdevice having a touch-sensitive display and intensity sensors inaccordance with some embodiments.

FIGS. 5E-5H illustrate exemplary components and user interfaces of apersonal electronic device in accordance with some embodiments.

FIGS. 6A-6V illustrate example user interfaces for accessing underwateruser interfaces in accordance with some embodiments.

FIGS. 7A-7G are flow diagrams of a process for accessing underwater userinterfaces in accordance with some embodiments.

DESCRIPTION OF EMBODIMENTS

The following description sets forth exemplary methods, parameters, andthe like. It should be recognized, however, that such description is notintended as a limitation on the scope of the present disclosure but isinstead provided as a description of exemplary embodiments.

There is a need for electronic devices that provide efficient methodsand interfaces for accessing underwater user interfaces displayed on theelectronic devices. Such techniques can reduce the cognitive burden on auser who accesses user interfaces while the electronic device is underwater, thereby enhancing productivity. Further, such techniques canreduce processor and battery power otherwise wasted on redundant userinputs.

Below, FIGS. 1A-1B, 2, 3, 4A-4B, and 5A-5H provide a description ofexemplary devices for performing the techniques for accessing underwateruser interfaces. FIGS. 6A-6V illustrate exemplary user interfaces whiledevice is under water. FIGS. 7A-7G are flow diagrams illustratingmethods of accessing underwater user interfaces in accordance with someembodiments. The user interfaces in FIGS. 6A-6V are used to illustratethe processes described below, including the processes in FIGS. 7A-7G.

Although the following description uses terms “first,” “second,” etc. todescribe various elements, these elements should not be limited by theterms. These terms are only used to distinguish one element fromanother. For example, a first touch could be termed a second touch, and,similarly, a second touch could be termed a first touch, withoutdeparting from the scope of the various described embodiments. The firsttouch and the second touch are both touches, but they are not the sametouch.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a,” “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

The term “if” is, optionally, construed to mean “when” or “upon” or “inresponse to determining” or “in response to detecting,” depending on thecontext. Similarly, the phrase “if it is determined” or “if [a statedcondition or event] is detected” is, optionally, construed to mean “upondetermining” or “in response to determining” or “upon detecting [thestated condition or event]” or “in response to detecting [the statedcondition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touchpads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse, and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience and is sometimes knownas or called a “touch-sensitive display system.” Device 100 includesmemory 102 (which optionally includes one or more computer-readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more contact intensity sensors 165 fordetecting intensity of contacts on device 100 (e.g., a touch-sensitivesurface such as touch-sensitive display system 112 of device 100).Device 100 optionally includes one or more tactile output generators 167for generating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on thetouch-sensitive surface, or to a substitute (proxy) for the force orpressure of a contact on the touch-sensitive surface. The intensity of acontact has a range of values that includes at least four distinctvalues and more typically includes hundreds of distinct values (e.g., atleast 256). Intensity of a contact is, optionally, determined (ormeasured) using various approaches and various sensors or combinationsof sensors. For example, one or more force sensors underneath oradjacent to the touch-sensitive surface are, optionally, used to measureforce at various points on the touch-sensitive surface. In someimplementations, force measurements from multiple force sensors arecombined (e.g., a weighted average) to determine an estimated force of acontact. Similarly, a pressure-sensitive tip of a stylus is, optionally,used to determine a pressure of the stylus on the touch-sensitivesurface. Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure, and the estimated force or pressureis used to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be accessible by the user on a reduced-size device withlimited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/orapplication-specific integrated circuits.

Memory 102 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or moremagnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices. Memory controller 122optionally controls access to memory 102 by other components of device100.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data. In some embodiments, peripheralsinterface 118, CPU 120, and memory controller 122 are, optionally,implemented on a single chip, such as chip 104. In some otherembodiments, they are, optionally, implemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The RF circuitry 108optionally includes well-known circuitry for detecting near fieldcommunication (NFC) fields, such as by a short-range communicationradio. The wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies, including but notlimited to Global System for Mobile Communications (GSM), Enhanced DataGSM Environment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n,and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, aprotocol for e-mail (e.g., Internet message access protocol (IMAP)and/or post office protocol (POP)), instant messaging (e.g., extensiblemessaging and presence protocol (XMPP), Session Initiation Protocol forInstant Messaging and Presence Leveraging Extensions (SIMPLE), InstantMessaging and Presence Service (IMPS)), and/or Short Message Service(SMS), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data is, optionally,retrieved from and/or transmitted to memory 102 and/or RF circuitry 108by peripherals interface 118. In some embodiments, audio circuitry 110also includes a headset jack (e.g., 212, FIG. 2). The headset jackprovides an interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, intensity sensor controller 159,haptic feedback controller 161, and one or more input controllers 160for other input or control devices. The one or more input controllers160 receive/send electrical signals from/to other input control devices116. The other input control devices 116 optionally include physicalbuttons (e.g., push buttons, rocker buttons, etc.), dials, sliderswitches, joysticks, click wheels, and so forth. In some alternateembodiments, input controller(s) 160 are, optionally, coupled to any (ornone) of the following: a keyboard, an infrared port, a USB port, and apointer device such as a mouse. The one or more buttons (e.g., 208, FIG.2) optionally include an up/down button for volume control of speaker111 and/or microphone 113. The one or more buttons optionally include apush button (e.g., 206, FIG. 2).

A quick press of the push button optionally disengages a lock of touchscreen 112 or optionally begins a process that uses gestures on thetouch screen to unlock the device, as described in U.S. patentapplication Ser. No. 11/322,549, “Unlocking a Device by PerformingGestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No.7,657,849, which is hereby incorporated by reference in its entirety. Alonger press of the push button (e.g., 206) optionally turns power todevice 100 on or off. The functionality of one or more of the buttonsare, optionally, user-customizable. Touch screen 112 is used toimplement virtual or soft buttons and one or more soft keyboards.

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output optionallyincludes graphics, text, icons, video, and any combination thereof(collectively termed “graphics”). In some embodiments, some or all ofthe visual output optionally corresponds to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor, or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. Touch screen 112 and display controller 156 (along with anyassociated modules and/or sets of instructions in memory 102) detectcontact (and any movement or breaking of the contact) on touch screen112 and convert the detected contact into interaction withuser-interface objects (e.g., one or more soft keys, icons, web pages,or images) that are displayed on touch screen 112. In an exemplaryembodiment, a point of contact between touch screen 112 and the usercorresponds to a finger of the user.

Touch screen 112 optionally uses LCD (liquid crystal display)technology, LPD (light emitting polymer display) technology, or LED(light emitting diode) technology, although other display technologiesare used in other embodiments. Touch screen 112 and display controller156 optionally detect contact and any movement or breaking thereof usingany of a plurality of touch sensing technologies now known or laterdeveloped, including but not limited to capacitive, resistive, infrared,and surface acoustic wave technologies, as well as other proximitysensor arrays or other elements for determining one or more points ofcontact with touch screen 112. In an exemplary embodiment, projectedmutual capacitance sensing technology is used, such as that found in theiPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.

A touch-sensitive display in some embodiments of touch screen 112 is,optionally, analogous to the multi-touch sensitive touchpads describedin the following U.S. patents: U.S. Pat. No. 6,323,846 (Westerman etal.), U.S. Pat. No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No.6,677,932 (Westerman), and/or U.S. Patent Publication 2002/0015024A1,each of which is hereby incorporated by reference in its entirety.However, touch screen 112 displays visual output from device 100,whereas touch-sensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 112 isdescribed in the following applications: (1) U.S. patent applicationSer. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2,2006; (2) U.S. patent application Ser. No. 10/840,862, “MultipointTouchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No.10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30,2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures ForTouch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patentapplication Ser. No. 11/038,590, “Mode-Based Graphical User InterfacesFor Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patentapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

Touch screen 112 optionally has a video resolution in excess of 100 dpi.In some embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user optionally makes contact with touchscreen 112 using any suitable object or appendage, such as a stylus, afinger, and so forth. In some embodiments, the user interface isdesigned to work primarily with finger-based contacts and gestures,which can be less precise than stylus-based input due to the larger areaof contact of a finger on the touch screen. In some embodiments, thedevice translates the rough finger-based input into a precisepointer/cursor position or command for performing the actions desired bythe user.

In some embodiments, in addition to the touch screen, device 100optionally includes a touchpad (not shown) for activating ordeactivating particular functions. In some embodiments, the touchpad isa touch-sensitive area of the device that, unlike the touch screen, doesnot display visual output. The touchpad is, optionally, atouch-sensitive surface that is separate from touch screen 112 or anextension of the touch-sensitive surface formed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 optionally also includes one or more optical sensors 164.FIG. 1A shows an optical sensor coupled to optical sensor controller 158in I/O subsystem 106. Optical sensor 164 optionally includescharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lenses, and converts thelight to data representing an image. In conjunction with imaging module143 (also called a camera module), optical sensor 164 optionallycaptures still images or video. In some embodiments, an optical sensoris located on the back of device 100, opposite touch screen display 112on the front of the device so that the touch screen display is enabledfor use as a viewfinder for still and/or video image acquisition. Insome embodiments, an optical sensor is located on the front of thedevice so that the user's image is, optionally, obtained for videoconferencing while the user views the other video conferenceparticipants on the touch screen display. In some embodiments, theposition of optical sensor 164 can be changed by the user (e.g., byrotating the lens and the sensor in the device housing) so that a singleoptical sensor 164 is used along with the touch screen display for bothvideo conferencing and still and/or video image acquisition.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112, which is located on the front of device 100.

Device 100 optionally also includes one or more proximity sensors 166.FIG. 1A shows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 is, optionally, coupled to inputcontroller 160 in I/O subsystem 106. Proximity sensor 166 optionallyperforms as described in U.S. patent application Ser. No. 11/241,839,“Proximity Detector In Handheld Device”; Ser. No. 11/240,788, “ProximityDetector In Handheld Device”; Ser. No. 11/620,702, “Using Ambient LightSensor To Augment Proximity Sensor Output”; Ser. No. 11/586,862,“Automated Response To And Sensing Of User Activity In PortableDevices”; and Ser. No. 11/638,251, “Methods And Systems For AutomaticConfiguration Of Peripherals,” which are hereby incorporated byreference in their entirety. In some embodiments, the proximity sensorturns off and disables touch screen 112 when the multifunction device isplaced near the user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112, which is located on thefront of device 100.

Device 100 optionally also includes one or more accelerometers 168. FIG.1A shows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 is, optionally, coupled to an inputcontroller 160 in I/O subsystem 106. Accelerometer 168 optionallyperforms as described in U.S. Patent Publication No. 20050190059,“Acceleration-based Theft Detection System for Portable ElectronicDevices,” and U.S. Patent Publication No. 20060017692, “Methods AndApparatuses For Operating A Portable Device Based On An Accelerometer,”both of which are incorporated by reference herein in their entirety. Insome embodiments, information is displayed on the touch screen displayin a portrait view or a landscape view based on an analysis of datareceived from the one or more accelerometers. Device 100 optionallyincludes, in addition to accelerometer(s) 168, a magnetometer (notshown) and a GPS (or GLONASS or other global navigation system) receiver(not shown) for obtaining information concerning the location andorientation (e.g., portrait or landscape) of device 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3)stores device/global internal state 157, as shown in FIGS. 1A and 3.Device/global internal state 157 includes one or more of: activeapplication state, indicating which applications, if any, are currentlyactive; display state, indicating what applications, views or otherinformation occupy various regions of touch screen display 112; sensorstate, including information obtained from the device's various sensorsand input control devices 116; and location information concerning thedevice's location and/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with, the30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and othertouch-sensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined threshold values without changing the trackpador touch screen display hardware. Additionally, in some implementations,a user of the device is provided with software settings for adjustingone or more of the set of intensity thresholds (e.g., by adjustingindividual intensity thresholds and/or by adjusting a plurality ofintensity thresholds at once with a system-level click “intensity”parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (liftoff) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast, or other visual property) ofgraphics that are displayed. As used herein, the term “graphics”includes any object that can be displayed to a user, including, withoutlimitation, text, web pages, icons (such as user-interface objectsincluding soft keys), digital images, videos, animations, and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which is, optionally, a component of graphicsmodule 132, provides soft keyboards for entering text in variousapplications (e.g., contacts 137, e-mail 140, IM 141, browser 147, andany other application that needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing; to camera 143 as picture/video metadata;and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 optionally include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   Contacts module 137 (sometimes called an address book or contact        list);    -   Telephone module 138;    -   Video conference module 139;    -   E-mail client module 140;    -   Instant messaging (IM) module 141;    -   Workout support module 142;    -   Camera module 143 for still and/or video images;    -   Image management module 144;    -   Video player module;    -   Music player module;    -   Browser module 147;    -   Calendar module 148;    -   Widget modules 149, which optionally include one or more of:        weather widget 149-1, stocks widget 149-2, calculator widget        149-3, alarm clock widget 149-4, dictionary widget 149-5, and        other widgets obtained by the user, as well as user-created        widgets 149-6;    -   Widget creator module 150 for making user-created widgets 149-6;    -   Search module 151;    -   Video and music player module 152, which merges video player        module and music player module;    -   Notes module 153;    -   Map module 154; and/or    -   Online video module 155.

Examples of other applications 136 that are, optionally, stored inmemory 102 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, contacts module 137 are, optionally, used to manage an address bookor contact list (e.g., stored in application internal state 192 ofcontacts module 137 in memory 102 or memory 370), including: addingname(s) to the address book; deleting name(s) from the address book;associating telephone number(s), e-mail address(es), physicaladdress(es) or other information with a name; associating an image witha name; categorizing and sorting names; providing telephone numbers ore-mail addresses to initiate and/or facilitate communications bytelephone 138, video conference module 139, e-mail 140, or IM 141; andso forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact/motionmodule 130, graphics module 132, and text input module 134, telephonemodule 138 are optionally, used to enter a sequence of characterscorresponding to a telephone number, access one or more telephonenumbers in contacts module 137, modify a telephone number that has beenentered, dial a respective telephone number, conduct a conversation, anddisconnect or hang up when the conversation is completed. As notedabove, the wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact/motion module 130, graphicsmodule 132, text input module 134, contacts module 137, and telephonemodule 138, video conference module 139 includes executable instructionsto initiate, conduct, and terminate a video conference between a userand one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages, and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages optionally include graphics, photos, audio files, videofiles and/or other attachments as are supported in an MMS and/or anEnhanced Messaging Service (EMS). As used herein, “instant messaging”refers to both telephony-based messages (e.g., messages sent using SMSor MMS) and Internet-based messages (e.g., messages sent using XMPP,SIMPLE, or IMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, map module 154, and music playermodule, workout support module 142 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data; calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store, and transmit workoutdata.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact/motion module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, text input module 134,and camera module 143, image management module 144 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, e-mail client module 140, and browser module 147,calendar module 148 includes executable instructions to create, display,modify, and store calendars and data associated with calendars (e.g.,calendar entries, to-do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, widget modules 149 aremini-applications that are, optionally, downloaded and used by a user(e.g., weather widget 149-1, stocks widget 149-2, calculator widget149-3, alarm clock widget 149-4, and dictionary widget 149-5) or createdby the user (e.g., user-created widget 149-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, the widget creator module 150are, optionally, used by a user to create widgets (e.g., turning auser-specified portion of a web page into a widget).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, search module 151 includes executable instructions to search fortext, music, sound, image, video, and/or other files in memory 102 thatmatch one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, and browser module 147, video and musicplayer module 152 includes executable instructions that allow the userto download and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present, or otherwise play back videos (e.g.,on touch screen 112 or on an external, connected display via externalport 124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, notes module 153 includes executable instructions to create andmanage notes, to-do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, and browser module 147, map module 154are, optionally, used to receive, display, modify, and store maps anddata associated with maps (e.g., driving directions, data on stores andother points of interest at or near a particular location, and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesinstructions that allow the user to access, browse, receive (e.g., bystreaming and/or download), play back (e.g., on the touch screen or onan external, connected display via external port 124), send an e-mailwith a link to a particular online video, and otherwise manage onlinevideos in one or more file formats, such as H.264. In some embodiments,instant messaging module 141, rather than e-mail client module 140, isused to send a link to a particular online video. Additional descriptionof the online video application can be found in U.S. Provisional PatentApplication No. 60/936,562, “Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos,” filed Jun. 20,2007, and U.S. patent application Ser. No. 11/968,067, “PortableMultifunction Device, Method, and Graphical User Interface for PlayingOnline Videos,” filed Dec. 31, 2007, the contents of which are herebyincorporated by reference in their entirety.

Each of the above-identified modules and applications corresponds to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (e.g., sets of instructions) need notbe implemented as separate software programs, procedures, or modules,and thus various subsets of these modules are, optionally, combined orotherwise rearranged in various embodiments. For example, video playermodule is, optionally, combined with music player module into a singlemodule (e.g., video and music player module 152, FIG. 1A). In someembodiments, memory 102 optionally stores a subset of the modules anddata structures identified above. Furthermore, memory 102 optionallystores additional modules and data structures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 is, optionally, reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g., inoperating system 126) and a respective application 136-1 (e.g., any ofthe aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripherals interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more viewswhen touch-sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected optionally correspond to programmatic levelswithin a programmatic or view hierarchy of the application. For example,the lowest level view in which a touch is detected is, optionally,called the hit view, and the set of events that are recognized as properinputs are, optionally, determined based, at least in part, on the hitview of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (e.g., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule 172, the hit view typically receives all sub-events related tothe same touch or input source for which it was identified as the hitview.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit or a higher level object from which application 136-1 inheritsmethods and other properties. In some embodiments, a respective eventhandler 190 includes one or more of: data updater 176, object updater177, GUI updater 178, and/or event data 179 received from event sorter170. Event handler 190 optionally utilizes or calls data updater 176,object updater 177, or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 include one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170 and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which optionally include sub-event deliveryinstructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation optionally also includes speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event (187) include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first liftoff (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second liftoff (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and liftoff of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (187) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers interact, or are enabled to interact, with one another. Insome embodiments, metadata 183 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc. on touchpads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward),and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 optionally also include one or more physical buttons, such as“home” or menu button 204. As described previously, menu button 204 is,optionally, used to navigate to any application 136 in a set ofapplications that are, optionally, executed on device 100.Alternatively, in some embodiments, the menu button is implemented as asoft key in a GUI displayed on touch screen 112.

In some embodiments, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, subscriber identity module(SIM) card slot 210, headset jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPUs) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM, or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above-identified elements in FIG. 3 is, optionally, storedin one or more of the previously mentioned memory devices. Each of theabove-identified modules corresponds to a set of instructions forperforming a function described above. The above-identified modules orprograms (e.g., sets of instructions) need not be implemented asseparate software programs, procedures, or modules, and thus varioussubsets of these modules are, optionally, combined or otherwiserearranged in various embodiments. In some embodiments, memory 370optionally stores a subset of the modules and data structures identifiedabove. Furthermore, memory 370 optionally stores additional modules anddata structures not described above.

Attention is now directed towards embodiments of user interfaces thatare, optionally, implemented on, for example, portable multifunctiondevice 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces are, optionally, implementedon device 300. In some embodiments, user interface 400 includes thefollowing elements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Messages;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online            Video;”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Maps;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, labeled            “Settings,” which provides access to settings for device 100            and its various applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 is labeled “Music” or “Music Player.” Other labels are,optionally, used for various application icons. In some embodiments, alabel for a respective application icon includes a name of anapplication corresponding to the respective application icon. In someembodiments, a label for a particular application icon is distinct froma name of an application corresponding to the particular applicationicon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 359) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 357 for generating tactile outputsfor a user of device 300.

Although some of the examples that follow will be given with referenceto inputs on touch screen display 112 (where the touch-sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments, the touch-sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse-based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

FIG. 5A illustrates exemplary personal electronic device 500. Device 500includes body 502. In some embodiments, device 500 can include some orall of the features described with respect to devices 100 and 300 (e.g.,FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitivedisplay screen 504, hereafter touch screen 504. Alternatively, or inaddition to touch screen 504, device 500 has a display and atouch-sensitive surface. As with devices 100 and 300, in someembodiments, touch screen 504 (or the touch-sensitive surface)optionally includes one or more intensity sensors for detectingintensity of contacts (e.g., touches) being applied. The one or moreintensity sensors of touch screen 504 (or the touch-sensitive surface)can provide output data that represents the intensity of touches. Theuser interface of device 500 can respond to touches based on theirintensity, meaning that touches of different intensities can invokedifferent user interface operations on device 500.

Exemplary techniques for detecting and processing touch intensity arefound, for example, in related applications: International PatentApplication Serial No. PCT/US2013/040061, titled “Device, Method, andGraphical User Interface for Displaying User Interface ObjectsCorresponding to an Application,” filed May 8, 2013, published as WIPOPublication No. WO/2013/169849, and International Patent ApplicationSerial No. PCT/US2013/069483, titled “Device, Method, and Graphical UserInterface for Transitioning Between Touch Input to Display OutputRelationships,” filed Nov. 11, 2013, published as WIPO Publication No.WO/2014/105276, each of which is hereby incorporated by reference intheir entirety.

In some embodiments, device 500 has one or more input mechanisms 506 and508. Input mechanisms 506 and 508, if included, can be physical.Examples of physical input mechanisms include push buttons and rotatablemechanisms. In some embodiments, device 500 has one or more attachmentmechanisms. Such attachment mechanisms, if included, can permitattachment of device 500 with, for example, hats, eyewear, earrings,necklaces, shirts, jackets, bracelets, watch straps, chains, trousers,belts, shoes, purses, backpacks, and so forth. These attachmentmechanisms permit device 500 to be worn by a user.

FIG. 5B depicts exemplary personal electronic device 500. In someembodiments, device 500 can include some or all of the componentsdescribed with respect to FIGS. 1A, 1B, and 3. Device 500 has bus 512that operatively couples I/O section 514 with one or more computerprocessors 516 and memory 518. I/O section 514 can be connected todisplay 504, which can have touch-sensitive component 522 and,optionally, intensity sensor 524 (e.g., contact intensity sensor). Inaddition, I/O section 514 can be connected with communication unit 530for receiving application and operating system data, using Wi-Fi,Bluetooth, near field communication (NFC), cellular, and/or otherwireless communication techniques. Device 500 can include inputmechanisms 506 and/or 508. Input mechanism 506 is, optionally, arotatable input device. Input mechanism 508 is, optionally, a button, insome examples.

Input mechanism 508 is, optionally, a microphone, in some examples.Personal electronic device 500 optionally includes various sensors, suchas GPS sensor 532, accelerometer 534, directional sensor 540 (e.g.,compass), gyroscope 536, motion sensor 538, and/or a combinationthereof, all of which can be operatively connected to I/O section 514.

Memory 518 of personal electronic device 500 can include one or morenon-transitory computer-readable storage mediums, for storingcomputer-executable instructions, which, when executed by one or morecomputer processors 516, for example, can cause the computer processorsto perform the techniques described below, including processes 700 (FIG.7). A computer-readable storage medium can be any medium that cantangibly contain or store computer-executable instructions for use by orin connection with the instruction execution system, apparatus, ordevice. In some examples, the storage medium is a transitorycomputer-readable storage medium. In some examples, the storage mediumis a non-transitory computer-readable storage medium. The non-transitorycomputer-readable storage medium can include, but is not limited to,magnetic, optical, and/or semiconductor storages. Examples of suchstorage include magnetic disks, optical discs based on CD, DVD, orBlu-ray technologies, as well as persistent solid-state memory such asflash, solid-state drives, and the like. Personal electronic device 500is not limited to the components and configuration of FIG. 5B, but caninclude other or additional components in multiple configurations.

As used here, the term “affordance” refers to a user-interactivegraphical user interface object that is, optionally, displayed on thedisplay screen of devices 100, 300, and/or 500 (FIGS. 1A, 3, and 5A-5B).For example, an image (e.g., icon), a button, and text (e.g., hyperlink)each optionally constitute an affordance.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider, or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch screen display(e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch screen display, a detected contact on the touch screen actsas a “focus selector” so that when an input (e.g., a press input by thecontact) is detected on the touch screen display at a location of aparticular user interface element (e.g., a button, window, slider, orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionally,based on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholdsoptionally includes a first intensity threshold and a second intensitythreshold. In this example, a contact with a characteristic intensitythat does not exceed the first threshold results in a first operation, acontact with a characteristic intensity that exceeds the first intensitythreshold and does not exceed the second intensity threshold results ina second operation, and a contact with a characteristic intensity thatexceeds the second threshold results in a third operation. In someembodiments, a comparison between the characteristic intensity and oneor more thresholds is used to determine whether or not to perform one ormore operations (e.g., whether to perform a respective operation orforgo performing the respective operation), rather than being used todetermine whether to perform a first operation or a second operation.

FIG. 5C illustrates detecting a plurality of contacts 552A-552E ontouch-sensitive display screen 504 with a plurality of intensity sensors524A-524D. FIG. 5C additionally includes intensity diagrams that showthe current intensity measurements of the intensity sensors 524A-524Drelative to units of intensity. In this example, the intensitymeasurements of intensity sensors 524A and 524D are each 9 units ofintensity, and the intensity measurements of intensity sensors 524B and524C are each 7 units of intensity. In some implementations, anaggregate intensity is the sum of the intensity measurements of theplurality of intensity sensors 524A-524D, which in this example is 32intensity units. In some embodiments, each contact is assigned arespective intensity that is a portion of the aggregate intensity. FIG.5D illustrates assigning the aggregate intensity to contacts 552A-552Ebased on their distance from the center of force 554. In this example,each of contacts 552A, 552B, and 552E are assigned an intensity ofcontact of 8 intensity units of the aggregate intensity, and each ofcontacts 552C and 552D are assigned an intensity of contact of 4intensity units of the aggregate intensity. More generally, in someimplementations, each contact j is assigned a respective intensity Ijthat is a portion of the aggregate intensity, A, in accordance with apredefined mathematical function, Ij=A·(Dj/ΣDi), where Dj is thedistance of the respective contact j to the center of force, and ΣDi isthe sum of the distances of all the respective contacts (e.g., i=1 tolast) to the center of force. The operations described with reference toFIGS. 5C-5D can be performed using an electronic device similar oridentical to device 100, 300, or 500. In some embodiments, acharacteristic intensity of a contact is based on one or moreintensities of the contact. In some embodiments, the intensity sensorsare used to determine a single characteristic intensity (e.g., a singlecharacteristic intensity of a single contact). It should be noted thatthe intensity diagrams are not part of a displayed user interface, butare included in FIGS. 5C-5D to aid the reader.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface optionally receives a continuous swipe contacttransitioning from a start location and reaching an end location, atwhich point the intensity of the contact increases. In this example, thecharacteristic intensity of the contact at the end location is,optionally, based on only a portion of the continuous swipe contact, andnot the entire swipe contact (e.g., only the portion of the swipecontact at the end location). In some embodiments, a smoothing algorithmis, optionally, applied to the intensities of the swipe contact prior todetermining the characteristic intensity of the contact. For example,the smoothing algorithm optionally includes one or more of: anunweighted sliding-average smoothing algorithm, a triangular smoothingalgorithm, a median filter smoothing algorithm, and/or an exponentialsmoothing algorithm. In some circumstances, these smoothing algorithmseliminate narrow spikes or dips in the intensities of the swipe contactfor purposes of determining a characteristic intensity.

The intensity of a contact on the touch-sensitive surface is,optionally, characterized relative to one or more intensity thresholds,such as a contact-detection intensity threshold, a light press intensitythreshold, a deep press intensity threshold, and/or one or more otherintensity thresholds. In some embodiments, the light press intensitythreshold corresponds to an intensity at which the device will performoperations typically associated with clicking a button of a physicalmouse or a trackpad. In some embodiments, the deep press intensitythreshold corresponds to an intensity at which the device will performoperations that are different from operations typically associated withclicking a button of a physical mouse or a trackpad. In someembodiments, when a contact is detected with a characteristic intensitybelow the light press intensity threshold (e.g., and above a nominalcontact-detection intensity threshold below which the contact is nolonger detected), the device will move a focus selector in accordancewith movement of the contact on the touch-sensitive surface withoutperforming an operation associated with the light press intensitythreshold or the deep press intensity threshold. Generally, unlessotherwise stated, these intensity thresholds are consistent betweendifferent sets of user interface figures.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold to an intensity between thelight press intensity threshold and the deep press intensity thresholdis sometimes referred to as a “light press” input. An increase ofcharacteristic intensity of the contact from an intensity below the deeppress intensity threshold to an intensity above the deep press intensitythreshold is sometimes referred to as a “deep press” input. An increaseof characteristic intensity of the contact from an intensity below thecontact-detection intensity threshold to an intensity between thecontact-detection intensity threshold and the light press intensitythreshold is sometimes referred to as detecting the contact on thetouch-surface. A decrease of characteristic intensity of the contactfrom an intensity above the contact-detection intensity threshold to anintensity below the contact-detection intensity threshold is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments, the contact-detection intensity threshold is zero.In some embodiments, the contact-detection intensity threshold isgreater than zero.

In some embodiments described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., a “down stroke” of the respective pressinput). In some embodiments, the press input includes an increase inintensity of the respective contact above the press-input intensitythreshold and a subsequent decrease in intensity of the contact belowthe press-input intensity threshold, and the respective operation isperformed in response to detecting the subsequent decrease in intensityof the respective contact below the press-input threshold (e.g., an “upstroke” of the respective press input).

FIGS. 5E-5H illustrate detection of a gesture that includes a pressinput that corresponds to an increase in intensity of a contact 562 froman intensity below a light press intensity threshold (e.g., “IT_(L)”) inFIG. 5E, to an intensity above a deep press intensity threshold (e.g.,“IT_(D)”) in FIG. 5H. The gesture performed with contact 562 is detectedon touch-sensitive surface 560 while cursor 576 is displayed overapplication icon 572B corresponding to App 2, on a displayed userinterface 570 that includes application icons 572A-572D displayed inpredefined region 574. In some embodiments, the gesture is detected ontouch-sensitive display 504. The intensity sensors detect the intensityof contacts on touch-sensitive surface 560. The device determines thatthe intensity of contact 562 peaked above the deep press intensitythreshold (e.g., “IT_(D)”). Contact 562 is maintained on touch-sensitivesurface 560. In response to the detection of the gesture, and inaccordance with contact 562 having an intensity that goes above the deeppress intensity threshold (e.g., “IT_(D)”) during the gesture,reduced-scale representations 578A-578C (e.g., thumbnails) of recentlyopened documents for App 2 are displayed, as shown in FIGS. 5F-5H. Insome embodiments, the intensity, which is compared to the one or moreintensity thresholds, is the characteristic intensity of a contact. Itshould be noted that the intensity diagram for contact 562 is not partof a displayed user interface, but is included in FIGS. 5E-5H to aid thereader.

In some embodiments, the display of representations 578A-578C includesan animation. For example, representation 578A is initially displayed inproximity of application icon 572B, as shown in FIG. 5F. As theanimation proceeds, representation 578A moves upward and representation578B is displayed in proximity of application icon 572B, as shown inFIG. 5G. Then, representations 578A moves upward, 578B moves upwardtoward representation 578A, and representation 578C is displayed inproximity of application icon 572B, as shown in FIG. 5H. Representations578A-578C form an array above icon 572B. In some embodiments, theanimation progresses in accordance with an intensity of contact 562, asshown in FIGS. 5F-5G, where the representations 578A-578C appear andmove upwards as the intensity of contact 562 increases toward the deeppress intensity threshold (e.g., “IT_(D)”). In some embodiments, theintensity, on which the progress of the animation is based, is thecharacteristic intensity of the contact. The operations described withreference to FIGS. 5E-5H can be performed using an electronic devicesimilar or identical to device 100, 300, or 500.

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some embodiments, the press inputis detected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the descriptions of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold.

Attention is now directed towards embodiments of user interfaces (“UI”)and associated processes that are implemented on an electronic device,such as portable multifunction device 100, device 300, or device 500.

FIGS. 6A-6V illustrate exemplary user interfaces for accessingunderwater user interfaces while an underwater mode is activated inaccordance with some embodiments. The user interfaces in these figuresare used to illustrate the processes described below, including theprocesses in FIGS. 7A-7G. As stated herein, an underwater mode isactivated for an electronic device such as device 100 if one or morecomponents of device 100, 300, or 500 of FIGS. 1A and 6A-6V, 3, or 5A,respectively, is wet, or is under water. In some embodiments, anunderwater mode is activated for an electronic device if at least athreshold percentage (e.g., 20%, 40%, 75%, or another percentage) of thesurface area of the electronic device or a component of the electronicdevice (e.g., display 112 of device 100) is wet or is under water. Insome embodiments, an underwater mode is activated for an electronicdevice if one or more ports (e.g., charging port 124 as illustrated inFIGS. 1A and 2) of the electronic device are wet. In some embodiments,an electronic device is wet if the ports and a threshold percentage ofthe surface area of a display of the electronic device are wet.Similarly, an underwater mode is not activated or is deactivated for anelectronic device such as device 100, 300, or 500, if at least athreshold percentage of the surface area of the electronic device or acomponent of the electronic device (e.g., display 112) is not wet, ifone or more ports of the electronic device are not wet, or if the portsand at least the threshold percentage of the surface area of theelectronic device are not wet.

In some embodiments, an electronic device such as device 100 determinesto activate an underwater mode if a first threshold percentage of thesurface area (e.g., 35, 90%, etc.) of a display (e.g., display 112) ofthe electronic device is wet and determines not to activate or todeactivate an underwater mode if a second threshold percentage of thesurface area (e.g., 25%, 55%, etc.) of its display is not wet. In someembodiments, an electronic device determines to activate an underwatermode if a first threshold percentage of the surface area of its display(e.g., display 112) is wet for a first threshold period of time (e.g.,one second, two seconds, 10 seconds, etc.) and determines not toactivate or to deactivate an underwater mode if a second thresholdpercentage of the surface area of its display is not wet for a secondthreshold period of time. In one or more of the foregoing embodiments,the values of the first threshold percentage of the surface area and thesecond threshold percentage of the surface area are different, and thevalues of the first threshold period of time and the second thresholdperiod of time are different. For example, device 100 determines toactivate an underwater mode after determining that charging port 124 iswet and that more than 50% of display 112 is wet. Device 100, afterdetermining to activate the underwater mode, determines to deactivatethe underwater mode if it determines that charging port 124 is no longerwet and that at least 75% of display 112 has not been wet for more thanfive seconds. In one or more of the foregoing embodiments, device 100automatically determines or adjusts the values of the first and thesecond thresholds. In one or more of the foregoing embodiments, thevalues of the first and second thresholds are adjustable by a user ofdevice 100. Additional descriptions of criteria for determining whetherto activate or deactivate an underwater mode for an electronic deviceare provided in the paragraphs below and are illustrated in at leastFIGS. 6A-6V.

While underwater mode is activated, an electronic device (e.g., device100, 300, or 500 or FIGS. 1A and 6A-6V, 3, or 5A, respectively)sometimes displays certain user interfaces (hereafter referred to as“underwater user interfaces”) containing user interface elements ofapplications and modules (e.g., camera, flashlight, alarm, timer, aswell as other applications and modules) that are accessible while theelectronic device is wet or under water, as well as user interfaceelements of settings and functions (e.g., camera modes, camera flash,delay shutter, repeat alarm, flashlight intensity, as well as othersettings and functions) of the applications and modules. In one or moreembodiments, underwater user interfaces contain menus of user interfaceelements of applications and modules that are accessible to a user whilethe electronic device is under water. In one or more embodiments,underwater user interfaces have different appearances and featuresrelative to corresponding non-underwater user interfaces, which are userinterfaces that are displayed on the electronic device while theelectronic device is not under water. For example, a user interface 5112of FIG. 6A, which is displayed on display 112 while device 100 is notunder water, has a different visual appearance relative to userinterfaces 5113 and 5114 of FIGS. 6C and 6H, respectively, which aredisplayed while device 100 is under water.

In some embodiments, the user performs different user inputs to interactwith corresponding content and user interfaces elements that aredisplayed in underwater user interfaces such as user interfaces 5113 and5114 vs. non-underwater user interfaces that are displayed on theelectronic device while the electronic device is not under water. Forexample, while device 100 is not under water, a user performs a tapgesture to access an application or a function of device 100 (e.g.,camera application, timer application, alarm application, flashlightapplication, or another application or function), whereas while device100 is under water, the user performs a deep press gesture (definedherein) to access the corresponding application or function of device100. In one or more of such embodiments, while underwater mode isactivated for device 100, device 100 treats a tap gesture as anaccidental input, and, in response to detecting the tap gesture,maintains display of the existing user interface without performingoperations associated with detecting the tap gesture if the tap gesturewas detected while device 100 was not under water. Additionaldescriptions of underwater user interfaces, corresponding non-underwateruser interfaces, and different user inputs performed by the user tointeract with an electronic device while the electronic device is underwater or not under water are illustrated in at least FIGS. 6A-6V.

Although some of the examples that follow will be given with referenceto inputs on a touch-screen display (where the touch-sensitive surfaceand the display are combined) such as touch-sensitive display 112, insome embodiments, the device detects inputs on a touch-sensitive surface451 that is separate from the display 450, as shown in FIG. 4B. In otherembodiments, the processes described herein may be implemented withdevices having physical user interfaces, voice interfaces, or othersuitable interfaces. For convenience of explanation, the embodimentsdescribed below will be discussed with reference to operations performedon a device with a touch-sensitive display system 112. In suchembodiments, a focus selector is, optionally: a respective finger orstylus contact, a representative point corresponding to a finger orstylus contact (e.g., a centroid of a respective contact or a pointassociated with a respective contact), or a centroid of two or morecontacts detected on the touch-sensitive display system 112. However,analogous operations are, optionally, performed on a device with adisplay 450 and a separate touch-sensitive surface 451 in response todetecting the contacts on the touch-sensitive surface 451 whiledisplaying the user interfaces discussed below, along with a focusselector.

FIG. 6A illustrates device 100 having display 112 while device 100 isnot under water. In the illustrated embodiment, user interface 5112,which contains application affordances 5020-5040, is displayed ondisplay 112 while device 100 is not under water. As stated herein, anapplication affordance is a user interface element that the userinteracts with to access user interfaces of a corresponding applicationthat runs on device 100. In the illustrated embodiment, cameraaffordance 5020 is an application affordance of a digital cameraapplication and flashlight affordance 5021 is an application affordanceof a flashlight application. The user optionally interacts with one ofapplication affordances 5020-5040 to access user interfaces of acorresponding application. In the illustrated embodiment, device 100also includes volume adjustment buttons 5012 and 5014 as well as pushbutton 5016. In the illustrated embodiment, and while device 100 is notunder water, a longer press of push button 5016 optionally turns powerto device 100 on or off, and presses of volume adjustment buttons 5012and 5014 optionally adjust volume output of device 100.

FIG. 6B illustrates device 100 of FIG. 6A after device 100 is partiallysubmerged in water or another liquid. In the illustrated embodiments ofFIGS. 6B-6V, waterline 5111 represents a level reached by water oranother liquid relative to device 100. More particularly, portions ofdevice 100 below waterline 5111 are submerged in water and are wet,whereas portions of device 100 above waterline 5111 are not submerged inwater. As display 112 becomes wet, device 100 determines whethercriteria (e.g., whether a threshold percentage of the surface area ofdisplay 112 is wet, whether charging port 124 is wet, etc.) fordetermining whether device 100 is under water are met. In theillustrated embodiment of FIG. 6B, although a portion of device 100(e.g., approximately 50%) is submerged, device 100 determines that lessthan a threshold percentage of the surface area of display 112 is wet.Device 100 then concludes that it is not under water. As such, userinterface 5112 remains displayed on display 112 even though a portion ofdevice 100 is wet.

FIG. 6C illustrates device 100 of FIG. 6B after device 100 is furthersubmerged in water. In the embodiment of FIG. 6C, device 100 isapproximately 75% submerged in water, which satisfies the thresholdpercentage of the wet surface area of display 112 for determining thatdevice 100 is under water. In some embodiments, device 100, afterdetermining that a threshold percentage of the surface area of device100 is wet, displays an underwater indicator, such as underwaterindicator 5018 on display 112. As stated herein, an underwater indicatoris a user interface element that provides a visual indication thatdevice 100 is under water. Although FIG. 6C illustrates underwaterindicator 5018 displayed in a status bar region of device 100,optionally, underwater indicator 5018 is displayed in another region ofdisplay 112. In some embodiments, the user optionally performs a gesturewith contact over underwater indicator 5018 to manually confirm thatdevice 100 is under water. In the depicted embodiment of FIG. 6C, device100, after determining that it is under water, automatically removes thedisplay of user interface 5112, and displays underwater user interface5113 on display 112. In the illustrated embodiment, underwater userinterface 5113 includes a menu of application affordances 5050-5053 ofapplications accessible to the user while device 100 is under water.

Underwater user interfaces, such as underwater user interface 5113 havedifferent appearances and characteristics relative to the appearancesand characteristics of non-underwater user interfaces. In one or more ofsuch embodiments, user interface elements that are displayed inunderwater user interfaces are arranged in a different order thancorresponding non-underwater user interfaces. In one or more of suchembodiments, underwater user interfaces have themes (e.g., backgroundimages that suggest that device 100 is under water) that are differentfrom themes of non-underwater user interfaces. In one or moreembodiments, the display size and shape of user interface elements(e.g., camera affordance 5050) when displayed in underwater userinterfaces are different than the display size of corresponding userinterface elements (e.g., camera affordance 5020) that are displayed innon-underwater user interfaces. In one or more embodiments, userinterface elements of underwater user interfaces are displayed in menuformats, where the user optionally switches between different userinterface elements by pressing one or more physical buttons, such asvolume adjustment buttons 5012 and 5014.

In one or more embodiments, only user interface elements of applicationsand functions that are available while device 100 is under water aredisplayed in underwater user interfaces to help the user identifyapplications and functions that are available while device 100 is underwater. For example, where a jukebox application is not available whiledevice 100 is under water, a jukebox affordance associated with thejukebox application and user interface elements associated withdifferent settings of the jukebox application are not displayed inunderwater user interfaces. Similarly, where a telephone module isdisabled while device 100 is under water, user interface elementsassociated with a telephone application and different settings andfunctions of the telephone module are not displayed in underwater userinterfaces. In one or more embodiments, underwater user interfacescontain user interface elements of applications and functions that arenot displayed on corresponding user interfaces while device 100 is notunder water. For example, where underwater user interface 5113 and userinterface 5112 are both wake screen user interfaces, which areinterfaces that are displayed on device 100 after device 100 is accessedafter a certain period of inactivity, underwater user interface 5113includes timer affordance 5052, alarm affordance 5053, and exitaffordance 5054. However, user interface 5112 as illustrated in FIG. 6Adoes not include a corresponding timer affordance, alarm affordance, orexit affordance. In one or more embodiments, underwater user interfacesinclude user interface elements of applications and functions that areuseful to the user or that are more useful to the user while device 100is under water. In one or more embodiments, the different appearancesand characteristics of underwater user interfaces help the user toidentify that device 100 is under water. In one or more embodiments,user interface elements are displayed in underwater user interfaces in aparticular arrangement or format to assist the user to select the userinterface elements while device 100 is under water. For example, thedisplay size of camera affordance 5050 is larger relative to the displaysize of corresponding camera affordance 5020 of FIG. 6A to provide theuser with a greater contact area to select camera affordance 5050 whiledevice 100 is under water.

While device 100 is under water, the user performs certain user inputsto select application affordances 5050-5053 or an exit affordance 5054.In some embodiments, the user selects one of the application affordances(e.g., camera affordance 5050) by pressing a physical button, such as bypressing push button 5016. In some embodiments, the user switchesbetween application affordances 5050-5053 and exit affordance 5054 bypressing a volume adjustment button 5012 or 5014. In some embodiments,the user selects any of the application affordances 5050-5053 or exitaffordance 5054 by performing a deep press gesture. As referred toherein, a deep press gesture is a gesture performed with an intensitythat is greater than or equal to a deep press intensity threshold. Inone or more embodiments, while underwater mode is activated for device100, device 100 does not respond to user inputs on display 112 that haveintensities less than the deep press intensity threshold (e.g., tap ordrag gestures that have less than the deep press intensity threshold) toavoid performing certain operations in response to accidental inputwhile device 100 is under water. Additional descriptions of user inputsto interact with user interface elements displayed in underwater userinterface 5113 of FIGS. 6C, 6G, 6P, 6Q, and underwater user interface5114 of FIG. 6H are described in paragraphs below and are illustrated inat least FIGS. 6C, 6H, 6G, 6P, and 6Q.

In some embodiments, device 100, after determining that it is underwater, adjusts certain settings and functions of device 100 to improveperformance and battery life while under water. In one or moreembodiments, device 100 automatically turns off certain modules andapplications that are unlikely to be used while under water orunavailable while under water. For example, device 100, afterdetermining that it is under water, automatically turns off acoustic,touch, and telephone modules, and closes music, podcast, and diaryapplications to conserve battery life. In one or more embodiments,device 100 automatically adjusts the functions of certain applicationsand modules while under water. For example, device 100, afterdetermining it is under water, automatically turns off display 112, orreduces the period of inactivity to turn off display 112 to conservebattery life. Further, device 100 also adjusts certain default settingsof applications and modules accessible to the user while device 100 isunder water to improve performance while device 100 is under water. Forexample, device 100 automatically adjusts flash, shutter, zoom, as wellas other camera settings while device 100 is under water to improveunderwater photography.

In some embodiments, device 100, while under water, activates a lostphone mode, which after a threshold period of inactivity (e.g., afterone minute, five minutes, or another threshold period of inactivity),causes device 100 to periodically emit a flash from device 100. In oneor more of such embodiments, device 100 automatically activates the lostphone mode after device 100 determines that it is under water. In one ormore embodiments, device 100 activates the lost phone mode after athreshold period (e.g., one minute, two minutes, five minutes, oranother period) of inactivity. In one or more embodiments, device 100,while in lost phone mode, emits a pattern of light beams (e.g., a strobepattern) that alternates one or more characteristics (e.g., intensity,color, frequency, or another characteristic) of the emitted light beams.

In some embodiments, device 100, while under water, or optionally, whilelost phone mode is activated, receives communication (e.g., a textmessage, a phone call, etc.) transmitted by an electronic device (e.g.,a second electronic device) of the user or a third party (e.g., acontact of the user, an emergency personnel, a nearby user, or anotherthird party). In one or more of such embodiments, device 100, inresponse to receiving the communication, displays the communication ondisplay 112. For example, device 100, in response to detecting a textmessage from the user's wife, overlays underwater user interface 5113with a message bubble containing the text message from the user's wife.In one or more embodiments, device 100, in response to receiving thecommunication transmitted from a second electronic device, alsodetermines a current position of device 100, and transmits signalsindicative of the current position of device 100 to the secondelectronic device. For example, device 100, in response to detecting arequest to initiate a phone call with the user's wife, overlaysunderwater user interface 5113 with a message bubble indicating that theuser's wife is calling. Further, device 100 also transmits signalsindicative of the current position of device 100 to the secondelectronic device together with a request to display the currentposition of device 100 on a display of the second electronic device. Inone or more of such embodiments, device 100 also transmits an indicationthat device 100 is currently under water to the second electronicdevice.

In some embodiments, device 100, while under water, or optionally, whilelost phone mode is activated, periodically transmits signals indicativeof the current position of device 100. In some embodiments, device 100,while under water, or optionally, while lost phone mode is activated,also periodically determines the position of device 100 relative to theposition of the second electronic device. In one or more embodiments,signals are automatically transmitted to electronic devices belonging toone or more contacts (e.g., family members, friends, or other contacts)of the user. In one or more embodiments, signals indicative of thecurrent position of device 100, the relative position of device 100, anda request for aid, are automatically transmitted to electronic devicesof emergency responders. In one or more embodiments, device 100 displaysa request to transmit signals indicative of the current position ofdevice 100 on display 112. Device 100, after receiving an inputconfirming the request or after not receiving any input for a thresholdperiod of time, transmits signals indicative of the current position ofdevice 100 to other electronic devices of contacts of the user,emergency personnel, or other third parties.

In some embodiments, device 100, while under water, or optionally, whilelost phone mode is activated, also requests other electronic devices ofone or more contacts to transmit a current location of the respectiveelectronic devices. For example, where the user is diving with a divinginstructor, device 100, periodically requests an electronic device(e.g., smartwatch) of the diving instructor to transmit a currentlocation of the diving instructor. Device 100 optionally displays thecurrent location of other electronic devices on display 112. Continuingwith the foregoing example, device 100, where device 100 periodicallyrequests the current location of the electronic device of the user'sdiving instructor, device 100 also displays the current location of thediving instructor's electronic device on display 112 to help the usertrack the location of the diving instructor.

FIG. 6D illustrates an alternative embodiment of FIG. 6C, where userinterface 5112 remains displayed in display 112 after device 100 isfurther submerged in water. In the illustrated embodiment of FIG. 6D,device 100 is approximately 75% submerged in water, which satisfies thecriteria for determining that device 100 is under water. Underwaterindicator 5018 is displayed in the status bar of device 100 to indicatethat device 100 is under water. However, although device 100 hasdetermined that it is under water, device 100 does not automaticallydisplay an underwater user interface, such as underwater user interface5113 of FIG. 6C. In one or more embodiments, device 100, afterdetermining that a threshold percentage of the surface area of display112 is wet, requests the user to confirm that device 100 is under water.For example, device 100, after determining that the threshold percentageof the surface area of display 112 is wet, displays a message box withuser interface elements that the user optionally selects to confirm orto deny that device 100 is under water. Device 100 then displays anunderwater user interface after receiving the user's confirmation thatthe device is under water. In one or more of such embodiments, device100 displays an underwater user interface after detecting certain userinputs to access an underwater user interface, such as after detecting adeep press gesture with contact over an application affordance (e.g.,camera affordance 5020) that is associated with an applicationaccessible while device 100 is under water.

FIG. 6E illustrates device 100 of FIG. 6D after device 100 is completelysubmerged in water. Underwater indicator 5018 is displayed in the statusbar of device 100 to indicate that device 100 is under water. Further,similar to FIG. 6D, although device 100 has determined that it is underwater, device 100 does not automatically display an underwater userinterface, such as underwater user interface 5113 of FIG. 6C. In theillustrated embodiment of FIG. 6E, device 100 maintains display of userinterface 5112 after it is initially submerged under water. FIGS. 6E-6Fillustrate detecting a tap gesture with contact 5502 over cameraaffordance 5020, where the intensity of the tap gesture is less than thedeep press intensity threshold, and in response to detecting the tapgesture, maintaining display of user interface 5112 without accessingthe camera application or displaying an underwater user interface. Inthe illustrated embodiment of FIGS. 6E-6F, user inputs with intensitiesthat are less than the deep press intensity threshold are treated bydevice 100 as accidental input while device 100 is under water, and donot cause device 100 to perform any operation in response to detectingsuch inputs. As such, device 100, in response to detecting the tapgesture illustrated in FIG. 6E, or any other gestures with contactintensities less than the deep press intensity threshold, maintainsdisplay of user interface 5112 without performing any operationsassociated with the performed gesture if the performed gesture wasdetected while device 100 is not under water.

FIGS. 6F-6G illustrate detecting a deep press gesture with contact 5504over camera affordance 5020, where the intensity of the deep pressgesture is greater than or equal to the deep press intensity threshold,and in response to detecting the deep press gesture, displayingunderwater user interface 5113 on display 112. In the illustratedembodiment of FIG. 6G, camera affordance 5050 is highlighted to indicatefocus on camera affordance 5050. While underwater user interface 5113 isdisplayed on display 112, the user optionally switches betweenapplication affordances 5050-5053 by pressing volume adjustment buttons5012 and 5014. Device 100, in response to detecting a press of a volumeadjustment button 5012 or 5014, moves focus to a different applicationaffordance 5051-5053, or to exit affordance 5054. For example, where theuser optionally presses volume adjustment button 5014 while focus is oncamera affordance 5050, device 100, in response to detecting the pressof volume adjustment button 5014, sets focus on flashlight affordance5051. Continuing with the foregoing example, where the user optionallypresses push button 5016 while focus is on flashlight affordance 5051,device 100, in response to detecting the press of push button 5016,accesses the flashlight application of device 100 and displays anunderwater flashlight user interface on display 112. Alternatively,where the user optionally presses volume adjustment button 5014 whilefocus is on flashlight affordance 5051, device 100, in response todetecting the press of volume adjustment button 5014, moves focus totimer application 5052. Continuing with the foregoing example, where theuser optionally presses push button 5016 while focus is on timeraffordance 5052, device 100, in response to detecting press of pushbutton 5016, accesses the timer application of device 100 and displaysan underwater timer user interface on display 112.

In some embodiments, the user optionally selects an applicationaffordance by performing a deep press gesture with contact over theapplication affordance. In some embodiments, where the user optionallypresses a volume adjustment button (e.g., volume adjustment button 5014)and holds the volume adjustment button for more than a threshold periodof time (e.g., one second, two seconds, etc.), device 100, in responseto detecting the press and hold of the volume adjustment button in adepressed state, toggles between application affordances 5050-5053 andexit affordance 5054. For example, where the user optionally presses andholds volume adjustment button 5014, device 100, in response todetecting the press and hold of volume adjustment button 5014, setsfocus on a different affordance for each one second increment (oranother threshold increment) the user holds volume adjustment button5014. For example, device 100, after detecting an initial press ofvolume adjustment button 5014 while focus is on camera affordance 5050,moves focus to flashlight affordance 5051. Further, device 100, afterdetecting the volume adjustment button 5014 is in the depressed statefor one second after the user pressed volume adjustment button 5014,moves focus to timer affordance 5052. Further, device 100, afterdetecting that the volume adjustment button 5014 is in the depressedstate for two seconds after the user pressed volume adjustment button5014, moves focus to alarm affordance 5053. Device 100 continues to movefocus to different affordances 5050-5054 until device 100 detects thatvolume adjustment button 5014 is no longer in the depressed state. Theuser optionally presses push button 5016 or performs a deep pressgesture with contact over the selected application affordance to accessan application associated with the selected application affordance.

In the embodiment of FIG. 6G, a list of application affordances5050-5053 and exit affordance 5054 is displayed in underwater userinterface 5113. In some embodiments, the underwater user interface has adifferent appearance than the appearance of underwater user interface5113. In that regard, FIGS. 6F and 6H illustrate detecting the deeppress gesture with contact 5504 over camera affordance 5020, and inresponse to detecting the deep press gesture, displaying underwater userinterface 5114 on display 112. In the illustrated embodiment of FIG. 6H,icons of application affordances 5050-5053 and exit affordance 5054 aredisplayed in underwater user interface 5114. The user optionallyperforms a deep press gesture with contact over any of applicationaffordances 5050-5053 or exit affordance 5054 to access a correspondingapplication or to exit underwater user interface 5114. Underwater userinterfaces 5113 and 5114 of FIGS. 6G and 6H, respectively, eachrepresents an exemplary embodiment of an underwater user interface thathas a different appearance than non-underwater user interfaces, such asuser interface 5112 of FIG. 6A. In one or more embodiments, device 100,in response to detecting the deep press gesture with contact 5504 asillustrated in FIG. 6F, displays a different underwater user interfacehaving a different appearance than the appearances of underwater userinterfaces 5113 and 5114.

FIGS. 6G and 6I illustrate, while underwater user interface 5113 isdisplayed on device 100, detecting a press of push button 5016 withcontact 5506 on push button 5016, and in response to detecting the pressof push button 5016, displaying an underwater camera user interface5115. Similarly, FIGS. 6H-6I illustrate detecting, while underwater userinterface 5114 is displayed on device 100, a deep press gesture withcontact 5508 over camera affordance 5050, and in response to detectingthe deep press gesture, displaying underwater camera user interface5115. As stated herein, an underwater camera user interface is a camerauser interface that is displayed while device 100 is under water.Further, while an underwater camera user interface such as underwatercamera user interface 5115 is displayed on display 112, the userperforms certain inputs (such as by pressing physical buttons 5012, 5014and 5016, or by performing deep press gestures) to access differentcamera features and settings. In the illustrated embodiment of FIG. 6I,three mode affordances 5150A-5150C (video mode affordance, photo modeaffordance, and square mode affordance, respectively) are displayed inunderwater camera user interface 5115. In the illustrated embodiment,focus is on photo mode affordance 5150B to indicate the current cameramode (photo mode) of device 100. The user optionally performs a deeppress gesture with contact over a different mode to change the cameramode. For example, device 100, in response to detecting a deep pressgesture with contact over video mode affordance 5150A, switches fromphoto mode to video mode. In one or more embodiments, device 100, inresponse to detecting a deep press gesture with contact over a differentmode affordance (e.g., video mode affordance 5150A), also displaysanother underwater user interface (e.g., underwater video userinterface) that is associated with the selected camera mode (e.g., videomode).

In some embodiments, where a non-underwater camera user interface isdisplayed on display 112, the user optionally scrolls through differentmode affordances such as mode affordances 5150A-5150C by performing aswipe gesture with contact from one mode affordance to another modeaffordance. For example, where a non-underwater camera user interfacealso contains mode affordances 5150A-5150C of FIG. 6I, the useroptionally performs a slide or drag gesture with contact from a regionof display 112 over photo mode affordance 5150B to another region ofdisplay 112 over video mode affordance 5150A. Device 100, in response todetecting the slide or drag gesture, switches from photo mode to videomode. However, in the embodiment of FIG. 6I, device 100, while underwater, treats slide and drag gestures as accidental input from the user,and in response to detecting a slide or a drag gesture, such as thepreviously described gesture with contact from a region of display 112over photo mode affordance 5150B to another region of display 112 overvideo mode affordance 5150A, maintains display of underwater camera userinterface 5115 and maintains the current camera mode (photo mode).

In the illustrated embodiment of FIG. 6I, a preview affordance 5150D,which contains a preview of a previously taken image, a take photoaffordance 5150E, which is an affordance the user interacts with to takea photo, and a switch camera affordance 5150F, which is an affordancethe user interfaces with to switch between different cameras (e.g.,front facing camera and rear facing camera) of device 100, are alsodisplayed in underwater camera user interface 5115. Further, an exitaffordance 5150G, which is an affordance the user interacts with to exitunderwater camera user interface 5115, a flash affordance 5150I, whichis an affordance the user interacts with to select flash settings, and atimer affordance 5150H, which is an affordance the user interacts withto delay the camera shutter, are also displayed in underwater camerauser interface 5115. In the illustrated embodiment, the user optionallyperforms a deep press gesture with contact over any of affordances5150A-5150I, and device 100, in response to detecting the deep pressgesture with contact over a respective affordance, performs acorresponding function associated with the selected affordance. Forexample, while a rear facing camera of device 100 is activated, the useroptionally performs a deep press gesture with contact over switch cameraaffordance 5150F to activate a front facing camera of device 100. Theuser then optionally performs a deep press gesture with contact overtake photo affordance 5150E to take a photo captured by the front facingcamera. However, device 100, while under water, ignores gestures withintensities that are less than the deep press intensity threshold. Forexample, if device 100, after detecting a tap gesture with contact overpreview affordance 5150D, determines that the intensity of the tapgesture is not greater than or equal to the deep press intensitythreshold, device 100 then maintains display of underwater camera userinterface 5115 as illustrated in FIG. 6I without displaying thepreviously taken photo (photo of a house) on display 112.

In the embodiment of FIG. 6I, the user optionally presses volumeadjustment buttons 5012 and 5014, or push button 5016 to initiatedifferent camera functions of device 100. In that regard, FIGS. 6J-6Killustrate detecting a press of volume adjustment button 5012 withcontact 5510 on volume adjustment button 5012, and in response todetecting the press of volume adjustment button 5012, increasing a zoomlevel of the camera from 1× zoom to 4× zoom.

In some embodiments, where a non-underwater camera user interface isdisplayed on display 112 while device 100 is not under water, the useroptionally performs a pinch gesture to adjust the current zoom level ofthe camera. For example, device 100, in response to detecting a pinchgesture with contact over a region of display 112 while device 100 isnot under water, adjusts the zoom level of the camera based on themagnitude of the pinch gesture. Further, where a non-underwater camerauser interface is displayed on display 112 while device 100 is not underwater, pressing the volume adjustment buttons does not cause device 100to adjust the zoom level of the camera. As such, device 100, in responseto detecting a press of volume adjustment button 5012 or 5014 while anon-underwater camera user interface is displayed on device 112,maintains display of the camera user interface without adjusting thezoom level of the camera. However, in the embodiment of FIG. 6K, wheredevice 100 is under water, device 100 treats pinch gestures asaccidental input from the user, and in response to detecting a pinchgesture, maintains display of underwater camera user interface 5115, andmaintains the current zoom level of the camera. In the illustratedembodiment, the user optionally presses volume adjustment button 5012again (or holds volume adjustment button 5012 after pressing volumeadjustment button 5012) to further increase the zoom level of thecamera. The user optionally presses volume adjustment button 5014 todecrease the zoom level of the camera, such as from 4× zoom to 2× zoom.The user optionally presses push button 5016 to take a photo at 4× zoom.In that regard, FIGS. 6K-6L illustrate detecting a press of push button5016 with contact 5512 on push button 5016, and in response to detectingthe press gesture, taking a photo with the rear facing camera of device100. Further, in the illustrated embodiment of FIG. 6L, previewaffordance 5150D has been updated to illustrate a photo of the mostrecently taken photo (photo of fish taken by rear facing camera at 4×zoom).

The user optionally presses physical buttons 5012, 5014, or 5016, orperforms deep press gestures over affordances 5150A-5150C and5150E-5150H to take additional photos or to adjust one or more camerasettings of device 100. In that regard, FIGS. 6M-6N illustrate detectinga press of volume adjustment button 5014 with contact 5513 on volumeadjustment button 5014, and in response to detecting the press of volumeadjustment button 5014, reducing the zoom level of the camera from 4×zoom to 1× zoom. Further, FIGS. 6N-6O illustrate detecting a deep pressgesture with contact over take photo affordance 5150E, and in responseto detecting the deep press gesture, taking a photo with the rear facingcamera of device 100 at 1× zoom level. Further, in the illustratedembodiment of FIG. 6O, preview affordance 5150D has been updated toillustrate a photo of the most recently taken photo (photo of two fishtaken by the rear facing camera of device 100 at 1× zoom). The useroptionally performs additional deep press gestures or presses ofphysical buttons 5012, 5014, and 5016 to adjust one or more camerasettings and modes, and to take additional photos or videos of theuser's surroundings.

FIGS. 6O-6P illustrate detecting a deep press gesture with contact 5516over exit affordance 5150G, and in response to detecting the deep pressgesture, removing display of underwater camera user interface 5115, andre-displaying underwater user interface 5113. Although FIG. 6Pillustrates displaying underwater user interface 5113, in one or moreembodiments, device 100, in response to detecting the deep press gestureas illustrated in FIG. 6O, displays underwater user interface 5114, oranother underwater user interface having a different appearance. Whileunderwater user interface 5113 is displayed on display 112, the useroptionally selects different application affordances 5050-5053 bypressing volume adjustment buttons 5012 and 5014. For example, where theuser optionally presses volume adjustment button 5014 while focus is oncamera affordance 5050, device 100, in response to detecting the pressof volume adjustment button 5014, sets focus on flashlight affordance5051. Continuing with the foregoing example, where the user optionallypresses push button 5016 while focus is on flashlight affordance 5051,device 100, in response to detecting the press of push button 5016,accesses the flashlight application of device 100 and displays anunderwater flashlight user interface on display 112.

In some embodiments, while underwater flashlight user interface isdisplayed, the user optionally presses one or more of physical buttonsto adjust settings of the flashlight application. For example, wheredevice 100, after detecting a press of push button 5016 while focus ison flashlight affordance 5051, displays an underwater flashlight userinterface and emits beams of light at a default intensity, the useroptionally presses volume adjustment button 5012 or volume adjustmentbutton 5014 to increase or decrease the intensity of the emitted beam oflight. In one or more embodiments, user interface elements associatedwith different flashlight settings are displayed in the underwaterflashlight user interface. For example, an increase light intensityaffordance and a decrease light intensity affordance are displayed inthe underwater flashlight user interface. The user optionally performs adeep press gesture with contact over the increase light intensityaffordance to increase the light intensity of the flashlight, andoptionally, performs a deep press gesture with contact over the decreaselight intensity affordance to decrease the light intensity of theflashlight.

Similarly, where the user optionally presses push button 5016 whilefocus is on timer affordance 5052, device 100, in response to detectingthe press of push button 5016, accesses the timer application of device100 and displays an underwater timer user interface on display 112. Insome embodiments, while the underwater timer user interface is displayedon display 112, the user optionally presses one or more of physicalbuttons to adjust settings of the timer application. For example, theuser optionally presses volume adjustment button 5012 or volumeadjustment button 5014 to increase or decrease the time (e.g., in onesecond increments, in one minute increments, in one hour increments, oranother increment of time) on the timer. The user, after pressing volumeadjustment button 5012 or 5014, optionally holds the depressed volumeadjustment button 5012 or 5014 to increase or decrease the time on thetimer. Further, the user, after inputting a desired time on the timer,optionally sets the timer by pressing push button 5016. In one or moreembodiments, user interface elements associated with different timersettings are displayed in the underwater timer user interface. Forexample, an increase second affordance, an increase minute affordance,an increase hour affordance, a decrease second affordance, a decreaseminute affordance, and a decrease hour affordance are displayed in theunderwater timer user interface. The user optionally performs a deeppress gesture with contact over the increase second affordance, theincrease minute affordance, or the increase hour affordance,respectively, to increase the timer in one second, one minute, or onehour increments, respectively. Similarly, the user optionally performs adeep press gesture with contact over the decrease second affordance, thedecrease minute affordance, or the decrease hour affordance,respectively, to decrease the timer in one second, one minute, or onehour increments, respectively.

Similarly, where the user optionally presses push button 5016 whilefocus is on alarm affordance 5053, device 100, in response to detectingthe press of push button 5016, accesses the alarm application of device100 and displays an underwater alarm user interface on display 112. Insome embodiments, while the underwater alarm user interface is displayedon display 112, the user optionally presses one or more of physicalbuttons to adjust one or more settings of the alarm application. Forexample, the user optionally presses volume adjustment button 5012 orvolume adjustment button 5014 to increase or decrease the scheduledalarm time (e.g., in one second increments, in one minute increments, inone hour increments, or another increment of time). Further, the user,after inputting a desired alarm time, optionally sets the alarm to gooff at the desired alarm time by pressing push button 5016. In one ormore embodiments, user interface elements associated with differentalarm settings are displayed in the underwater alarm user interface. Forexample, an AM affordance, a PM affordance, and a repeat alarmaffordance are displayed in the underwater alarm user interface. Theuser optionally performs a deep press gesture with contact over the AMaffordance to designate the alarm to go off before midday, performs adeep press gesture with contact over the PM affordance to designate thealarm to go off after midday, and performs a deep press gesture withcontact over the repeat alarm affordance to designate the alarm to gooff every cycle (e.g., once every 24 hours, once every 12 hours or onceevery predetermined or user defined period of time). In someembodiments, an increase second affordance, an increase minuteaffordance, an increase hour affordance, a decrease second affordance, adecrease minute affordance, and a decrease hour affordance are alsodisplayed in the underwater alarm user interface. In one or moreembodiments, user interface elements associated with a number pad aredisplayed in the underwater alarm user interface. The user optionallyperforms deep press gestures over numbers associated with the desiredtime for the alarm to go off to input the desired alarm time.

FIGS. 6P-6Q illustrate detecting a press of volume adjustment button5012 with contact 5518 on volume adjustment button 5012, and in responseto detecting the press of volume adjustment button 5012, setting focuson exit affordance 5054. Further, FIGS. 6Q-6R illustrate detecting apress of push button 5016 with contact 5520 on push button 5016, and inresponse to detecting the press of push button 5016, displaying userinterface 5112 on display 112. In the embodiment of FIG. 6R, althoughthe user has manually exited underwater user interface 5113, device 100remains under water. As such, device 100 treats gestures havingintensities less than the deep press gesture intensity threshold asaccidental input. For example, while device 100 is under water, device100 detects a tap gesture similar to the tap gesture illustrated in FIG.6E with contact 5502 over camera affordance 5020. Device 100, inresponse to detecting the tap gesture, treats the tap gesture as anaccidental input and maintains display of user interface 5112 withoutdisplaying an underwater camera user interface or an underwater userinterface to access the camera of device 100. However, while device 100is under water, the user optionally performs deep press gestures toaccess applications (e.g., camera application) associated with userinterface elements that are displayed in user interface 5112. In thatregard, FIGS. 6R-6S illustrate detecting a deep press gesture withcontact 5522 over camera affordance 5020, and in response to detectingthe deep press gesture, re-displaying underwater user interface 5113 ondisplay 112.

FIGS. 6T and 6U illustrate gradually raising device 100 above waterline5111, where approximately 5% of device 100 is no longer wet in theembodiment of FIG. 6T and approximately 50% of device 100 is no longerwet in the embodiment of FIG. 6U. In the embodiments of FIGS. 6T and 6U,although a portion of device 100 is no longer wet, device 100 determinesthat the percentage of the surface area of display 112 that is not wetis less than a threshold value for determining that device is no longerunder water. Device 100 then determines that it is still underwater andmaintains display of underwater user interface 5113.

FIGS. 6U-6V illustrates further raising device 100 above waterline 5111.In the embodiment of FIG. 6V, approximately 25% of device 100 remainssubmerged. In the illustrated embodiment of FIG. 6V, device 100determines that the percentage of the surface area of display 112 thatis not wet is greater than or equal to the threshold value fordetermining that the device 100 is no longer under water, andsubsequently determines that device 100 is no longer under water, anddeactivates the underwater mode. In some embodiments, device 100determines that it is no longer under water if a threshold percentage ofthe surface area of display 112 is no longer wet for a threshold periodof time (e.g., at least 50% of display 112 is not wet for one second,five seconds, 15 seconds, or another period of time). In the illustratedembodiment of FIG. 6V, device 100, in response to determining that it isno longer under water, automatically deactivates the underwater mode andremoves the display of underwater user interface 5113 of FIG. 6U, anddisplays user interface 5112. In one or more embodiments, device 100deactivates the underwater mode and removes the display of an underwateruser interface such as underwater user interface 5113 after determiningthat it is no longer under water for a threshold period of time. In oneor more embodiments, device 100 deactivates the underwater mode andremoves the display of an underwater user interface after determiningthat the user has not inputted any inputs (e.g., gestures on display 112or presses of physical buttons) within a threshold period of time (e.g.,within five second after device 100 is no longer under water or anotherperiod of time) to provide a smooth transition from an underwater userinterface to a non-underwater user interface.

After device 100 deactivates the underwater mode, gestures havingintensities that are less than the deep press intensity threshold are nolonger treated by device 100 as accidental input. For example, device100, after deactivating underwater mode, detects a tap gesture similarto the tap gesture illustrated in FIG. 6E with contact 5502 over cameraaffordance 5020, and in response to detecting the gesture, displays acamera user interface on display 112. In some embodiments, after device100 deactivates the underwater mode, device 100 no longer displaysunderwater user interfaces (e.g., underwater user interface 5113 of FIG.6C). For example, where the user performs a tap gesture with contactover camera 5020 after device 100 is no longer under water, device 100,in response to detecting the tap gesture, displays a camera userinterface without displaying underwater user interface 5113 or otherunderwater user interfaces. In some embodiments, device 100 afterdeactivating underwater mode, automatically reactivates certain modulesthat were previously deactivated while device 100 was under water. Forexample, where device 100 deactivated the phone module after determiningthat it was under water, device 100, after determining that it is nolonger under water, automatically reactivates the phone module. In oneor more embodiments, device 100 also displays a notification on display112 to notify the user which previously deactivated modules have beenreactivated.

FIGS. 7A-7G are flow diagrams illustrating various embodiments of amethod for accessing underwater user interfaces. More particularly,FIGS. 7A-7G are flow diagrams illustrating a method for accessingunderwater user interfaces, using, for example, the user interfaces ofFIGS. 6A-6V. As described in reference to FIGS. 6A-6V, method 700 can beutilized to access underwater user interfaces. Method 700 is performedat a device (e.g., device 100, 300, 500 illustrated in FIGS. 1, 3, and5A, respectively) with a display and one or more input devices. In oneof such embodiments, the display is a touch screen display and thetouch-sensitive surface is on or integrated with the display. In someembodiments, the display is separate from the touch-sensitive surface.In some embodiments, the processes described herein may be implementedwith devices having physical user-interfaces, voice interfaces, or othersuitable interfaces. Some operations in method 700 are, optionally,combined and/or the order of some operations is, optionally, changed.

As described below, method 700 provides an intuitive way to accessunderwater user interfaces. Method 700 allows the user to access certainuser interfaces of applications running on device 100 while device 100is under water and other user interfaces of applications running ondevice 100 while device 100 is not under water. The foregoing allows theuser to access certain applications and modules that are accessiblewhile the user is under water, thereby reducing the cognitive burden onthe user. Method 700 also provides the user with easy access todifferent applications and modules that are available to the user whiledevice 100 is operating in different environments, thereby also reducingthe cognitive burden on the user and creating a more efficienthuman-machine interface. For battery-operated computing devices,enabling a user to use device 100 in different environments, such as inunderwater environments, faster and more efficiently conserves power andincreases the time between battery charges.

At an electronic device (e.g., device 100) with a display and one ormore input devices, receive (702) a first request to display a userinterface for accessing a first function of device 100. FIG. 6F, forexample, illustrates detecting a deep press gesture with contact 5504over camera affordance 5020. In the illustrated embodiment of FIG. 6A,where device 100 is not under water, the user optionally performs a tapgesture with contact over camera affordance 5020 to access camerafunctions of device 100.

Device 100, in response to receiving the first request, and inaccordance with a determination that device 100 is under water, displays(704) a first user interface for accessing the first function. FIGS.6F-6G, for example, illustrate device 100 while it is under water.Further, FIGS. 6F-6G illustrate detecting a deep press gesture withcontact 5504 over camera affordance 5020 while device 100 is underwater, and in response to detecting the deep press gesture, and inaccordance with a determination that device 100 is under water,displaying underwater user interface 5113 on display 112.

Device 100, in response to receiving the first request, and inaccordance with a determination that device 100 is not under water,displays (706) a second user interface for accessing the first function.In the illustrated embodiment of FIG. 6A, where device 100 is not underwater, the user optionally performs a tap gesture with contact overcamera affordance 5020, and device 100, in response to detecting the tapgesture, displays a camera user interface on display 112. Similarly, inthe illustrated embodiment of FIG. 6V, where device 100 is no longerunder water, the user optionally performs a tap gesture with contactover flashlight affordance 5021, and device 100, in response todetecting the tap gesture, displays a flashlight user interface ondisplay 112. In some embodiments, while device 100 is not under water,the user performs certain gestures (e.g., tap or slide gestures or othergestures having contact intensities less than the threshold deep pressintensity threshold) over user interface elements (e.g., take photoaffordance, delay shutter affordance, flash affordance, as well as otheraffordances associated with different camera settings and functions)displayed in the camera user interface to adjust different camerasettings and functions.

In some embodiments, device 100, while displaying the first userinterface, detects (708), via the one or more input devices, a firstuser input to access the first function. In some embodiments, device100, in accordance with a determination that the first user input is afirst type of user input, accesses (708) the first function from thefirst user interface. FIGS. 6F-6G, for example, illustrate detecting adeep press gesture with contact 5504 over camera affordance 5020, and inresponse to detecting the deep press gesture, displaying underwater userinterface 5113. In the illustrated embodiment of FIGS. 6F-6G, the firsttype of input include deep press gestures. In one or more embodiments,the first type of input also includes pressing physical buttons, such asphysical buttons 5012, 5014, and 5016 of FIGS. 6A-6V. In someembodiments, device 100, in accordance with a determination that thefirst user input is not the first type of user input, maintains displays(708) of the first user interface without accessing the first function.FIGS. 6E-6F, for example, illustrate detecting a tap gesture withcontact 5502 over camera affordance 5020, where the detected intensityof the tap gesture is less than the deep press intensity threshold, andin response to detecting the tap gesture, maintaining display of userinterface 5112 without accessing the camera application. In theillustrated embodiment of FIGS. 6E-6G, tap gestures having intensitiesless than the deep press intensity threshold do not belong to the firsttype of user input and are treated by device 100 as accidental input.

In some embodiments, device 100, while displaying the second userinterface, detects (708), via the one or more input devices, a seconduser input to access the first function. In some embodiments, device100, in accordance with a determination that the second user input is asecond type of user input, accesses (708) the first function from thesecond user interface. In the illustrated embodiment of FIG. 6A, whileuser interface 5112 is displayed on display 112, the user optionallyperforms a tap gesture with contact over camera affordance 5020. In theillustrated embodiment of FIG. 6A, the tap gesture, as well as othertypes of gestures having intensities less than the deep press intensitythreshold belong to the second type of user inputs whereas deep pressgestures do not belong to the second type of user inputs. Device 100, inresponse to detecting the tap gesture, displays a non-underwater camerauser interface on display 112. Continuing with the foregoing example,where the camera user interface includes user interface elements thatthe user interacts with to adjust different settings of the camera, theuser performs tap gestures with contacts over the user interfaceelements to adjust the settings and functions of the camera.

In some embodiments, device 100, in accordance with a determination thatthe second user input is not the second type of user input, maintainsdisplay (708) of the second user interface without accessing the firstfunction. In the embodiment of FIG. 6A, where device 100 is not underwater, the user optionally presses volume adjustment button 5012 or5014, each of which, is an input that does not belong to the second typeof inputs. Device 100, in response to detecting a press of volumeadjustment button 5012 or 5014, maintains display of user interface 5112without accessing the camera application of device 100. Similarly, wherea non-underwater camera user interface is displayed while device 100 isnot under water, device 100, in response to detecting a press of volumeadjustment button 5012 or 5014, maintains displaying of thenon-underwater camera user interface without adjusting the camera zoomsettings. Allowing different types of user inputs to access differentfunctions based on whether device 100 is under water or not under water,or based on whether underwater user interfaces are displayed, allows auser to use one type of gestures (e.g., tap gestures) to access certainfunctions of device 100 while device 100 is not under water, and allowsthe user to use a different type of gesture (e.g., deep press gestures)to access corresponding functions of device 100 while device is underwater, thereby reducing the cognitive burden of the user. Further, whiledevice 100 is under water, allowing the user to access certain functionsby performing only certain types of gestures, such as deep pressgestures, reduces a likelihood of accidental user input while device 100is under water, thereby creating a more efficient human-machineinterface. Further, while device 100 is not under water, the likelihoodof accidental input is less than the likelihood of accidental inputwhile device 100 is under water. In such environments, allowing the userto access certain functions or settings by performing other types ofinputs, such as tap gestures, which require less time and effort tocomplete, increases the efficiency and rate at which inputs are entered,thereby also creating a more efficient human-machine interface. Forbattery-operated computing devices, enabling a user to access differentfunctions of device 100 faster, more efficiently, and with less errorwhile device 100 is under water and while device 100 is not under waterconserves power and increases time between battery charges.

In some embodiments, the first user interface has a first appearance,and where the second user interface has a second appearance that isdifferent from the first appearance (710). FIG. 6C, for exampleillustrates underwater user interface 5113, which has a differentappearance than user interface 5112 of FIG. 6A. In the embodiment ofFIG. 6C, user interface elements of functions and applications of device100 are arranged in a menu format whereas in the embodiment of FIG. 6A,user interface elements of functions and applications of device 100 arearranged in rows and columns. Further, FIG. 6I illustrates underwatercamera user interface 5115. In some embodiments, certain user interfaceelements (e.g., exit affordance 5150G), which are displayed inunderwater camera user interface 5115, are not displayed innon-underwater camera user interfaces. Displaying underwater userinterfaces and non-underwater user interfaces in different appearancesallows the user to quickly recognize whether device 100 is under wateror not under water, thereby reducing the cognitive burden on the userand creating a more efficient human-machine interface. Further, allowingthe user to quickly recognize whether device 100 is under water or notunder water also allows the user to quickly determine which types ofuser inputs to enter (e.g., tap gestures vs. deep press gestures), whichreduces incorrect inputs. For battery-operated computing devices,enabling a user to quickly determine which types of inputs to enterfaster and more efficiently, and helping the user avoid enteringincorrect inputs, conserves power and increases time between batterycharges.

In some embodiments, device 100 receives (712) a second request todisplay a user interface for accessing a second function of the device100. In some embodiments, device 100, in response to receiving thesecond request, and in accordance with a determination that the device100 is under water, displays (712) the first user interface foraccessing the second function. In some embodiments, device 100, whiledisplaying the first user interface, detects (712), via the one or moreinput devices, a first user input to access the second function. In someembodiments, device 100, in accordance with a determination that thefirst user input is a first type of user input, accesses (712) thesecond function from the first user interface. In some embodiments,device 100, in accordance with a determination that the first user inputis not the first type of user input, maintains (712) display of thefirst user interface without accessing the second function. FIG. 6F, forexample, illustrates device 100 while device 100 is under water. In someembodiments, user optionally performs a deep press gesture (a first typeof user input) with contact over flashlight affordance 5021. Device 100,in response to detecting the deep press gesture, displays underwateruser interface 5113 as illustrated in FIG. 6E for accessing theflashlight application. The user optionally performs a deep pressgesture with contact over flashlight affordance 5051 of FIG. 6E, anddevice 100, in response to detecting the deep press gesture, accessesthe flashlight application and displays an underwater flashlight userinterface on display 112. In some embodiments, the user performs a tapgesture (second type of user input) over flashlight affordance 5051.However, in such embodiments, device 100 does not respond to the tapgesture. More particularly, device 100, in response to the tap gesture,maintains display of underwater user interface 5113 without accessingthe flashlight application.

In some embodiments, device 100, in response to receiving the secondrequest, and in accordance with a determination that the device 100 isnot under water, displays (712) the second user interface for accessingthe second function. In some embodiments, device 100, while displayingthe second user interface, detects (712), via the one or more inputdevices, a second user input to access the second function. In someembodiments, device 100, after displaying the second user interface, andin accordance with a determination that a second type of user input isperformed while the second user interface is displayed, accesses (712)the second function from the second user interface. In some embodiments,device 100, after displaying the second user interface, and inaccordance with a determination that the second type of user input isnot performed while the second user interface is displayed, maintains(712) display of the second user interface without accessing the secondfunction. FIG. 6A, for example, illustrates device 100 while device 100is not under water. In some embodiments, the user optionally performs atap gesture with contact over flashlight affordance 5021 of FIG. 6A toaccess the flashlight application, and device 100, in response todetecting the tap gesture, displays a non-underwater flashlight userinterface with user interface elements that the user interacts with toaccess or adjust one or more flashlight settings or functions, such asthe intensity of the flashlight, the color of the emitted light, thepattern of the emitted light, as well as other flashlight settings.While device 100 is not under water and while the non-underwaterflashlight user interface is displayed on display 112, the useroptionally performs tap or slide gestures (first type of user input) toaccess or adjust one or more settings or functions of the flashlight.Further, while device 100 is not under water and while thenon-underwater flashlight user interface is displayed on display 112,the user optionally presses one or more of physical buttons 5012, 5014,and 5016 (second type of user input). However, device 100, in responseto detecting pressing of physical buttons, 5112, 5114, or 5116,maintains display of the flashlight user interface without accessing oradjusting one or more settings or functions of the flashlight.

Displaying different user interfaces that have different appearancesbased on whether device 100 is under water or not under water helps theuser identify whether device 100 is under water or not under water,thereby reducing the cognitive burden of the user. Further, allowing theuser to access certain settings or functions by performing only certaintypes of gestures, such as deep press gestures, reduces a likelihood ofaccidental user input while device 100 is under water, thereby creatinga more efficient human-machine interface. Further, while device 100 isnot under water, the likelihood of accidental input is less than thelikelihood of accidental input while device 100 is under water. In suchenvironments, allowing the user to access certain functions or settingsby performing other types of inputs, such as tap gestures, which requireless time and effort to complete, increases the efficiency and rate atwhich inputs are entered, also creates a more efficient human-machineinterface. For battery-operated computing devices, enabling a user toaccess different functions of device 100 faster, more efficiently, andwith less error while device 100 is under water and while device 100 isnot under water conserves power and increases time between batterycharges.

In some embodiments, device 100, while displaying the first userinterface, detects (714), via the one or more input devices, a firstuser input to interact with a physical button of device 100. In someembodiments, device 100, in response to detecting the first user input,performs (714) the first function. FIGS. 6J-6K, for example, illustratesdetecting a press of volume adjustment button 5012 with contact 5510 onvolume adjustment button 5012, and in response to detecting the press ofvolume adjustment button 5012, performing a zoom in function.

In some embodiments, device 100, in response to receiving the firstrequest, and in accordance with a determination that device 100 is notunder water, displays (714) a first user interface element that isassociated with the first function in the second user interface. In someembodiments, device 100 detects (714), via the one or more inputdevices, a second user input to select the first user interface element.In some embodiments, device 100, in accordance with a determination thatthe second user input is a drag input performed over the first userinterface element, performs (714) the first function. In someembodiments, device 100, in accordance with a determination that thesecond user input is not a drag input performed over the first userinterface element, maintains display (714) of the first user interfaceelement without performing the first function. FIG. 6A, for example,illustrates device 100 while device 100 is not under water. In someembodiments, the user optionally performs a tap gesture with contactover camera affordance 5020 of FIG. 6A, and device 100, in response todetecting the tap gesture, displays a non-underwater camera userinterface. In one or more embodiments, the user performs a drag gesture(or a pinch gesture) with contact on display 112, and device 100, inresponse to detecting the drag gesture (or the pinch gesture), adjuststhe zoom of the camera. Further, in one or more embodiments, where thenon-underwater camera user interface is displayed on display 112, theuser presses volume adjustment buttons 5012 and 5014 of device 100.However, device 100, in response to detecting pressing of volumeadjustment buttons 5012 and 5014, maintains display of thenon-underwater camera user interface without adjusting the zoom level ofthe camera.

While device is under water, performing certain functions (e.g.,adjusting the zoom level, changing the camera mode, switching betweenfront and rear facing cameras, taking a photo, as well as performingother functions) in response to detecting certain types of gestures,such as pressing physical buttons 5012, 5014, or 5016 of device 100,reduces a likelihood of accidental user input while device 100 is underwater, thereby creating a more efficient human-machine interface.Further, while device 100 is not under water, the likelihood ofaccidental input is less than the likelihood of accidental input whiledevice 100 is under water. In such environments, performing certainfunctions in response to detecting other types of inputs, such as draggestures, which require less time and effort to complete, increases theefficiency and rate at which inputs are entered, also creates a moreefficient human-machine interface. For battery-operated computingdevices, enabling a user to access different functions of device 100faster, more efficiently, and with less error while device 100 is underwater and while device 100 is not under water conserves power andincreases time between battery charges.

In some embodiments, device 100, in response to receiving the firstrequest, and in accordance with a determination that device 100 is underwater, displays (716) a first user interface element that is associatedwith the first function in the first user interface. In someembodiments, device 100 detects (716), via the one or more inputdevices, a first user input to select the first user interface element.In some embodiments, device 100, in accordance with a determination thatthe first user input is an input with an intensity above a respectiveintensity threshold detected at a location corresponding to the firstuser interface element, performs (716) the first function. In someembodiments, device 100, in accordance with a determination that thefirst user input is an input with an intensity that is not above therespective intensity threshold detected at the location corresponding tothe first user interface element; maintains display (716) of the firstuser interface element without performing the first function. FIG. 6I,for example, illustrates displaying underwater camera user interface5115 while device 100 is under water. Moreover, focus is set on photomode affordance 5150B to indicate that the camera is in photo mode. Insome embodiments, the user optionally performs a deep press gesture withcontact over video mode affordance 5150A. Device 100, in response todetecting the deep press gesture, moves focus to video mode affordance5150A and changes the camera mode from photo mode to video mode. In someembodiments, the user optionally performs a tap gesture with contactover video mod affordance 5150A. Device 100, in response to detectingthe tap gesture, treats the tap gesture as an accidental input andmaintains display of underwater camera user interface 5115 withoutchanging the camera mode.

In some embodiments, device 100, in response to receiving the firstrequest, and in accordance with a determination that device 100 is notunder water, displays (716) a second user interface element that isassociated with the first function in the second user interface. In someembodiments, device 100 detects (716), via the one or more inputdevices, a second user input to select the second user interfaceelement. In some embodiments, device 100, in accordance with adetermination that the second user input is a drag input performed overthe second user interface element, performs (716) the first function. Insome embodiments, device 100, in accordance with a determination thatthe second user input is not a drag input performed over the second userinterface element, maintains display (716) of the second user interfaceelement without performing the first function. FIG. 6A, for example,illustrates device 100 while device 100 is not under water. In someembodiments, the user optionally performs a tap gesture with contactover camera affordance 5020 of FIG. 6A, and device 100, in response todetecting the tap gesture, displays a non-underwater camera userinterface. In one or more embodiments, the user performs a drag gesturewith contact from photo mode affordance 5150B to video mode affordance5150A, and device 100, in response to detecting the drag gesture,changes the camera mode from photo mode to video mode. Further, in oneor more embodiments, where the non-underwater camera user interface isdisplayed on display 112 while device 100 is not under water, the useroptionally presses volume adjustment buttons 5012 and 5014 of device100. However, device 100, in response to detecting pressing of volumeadjustment buttons 5012 and 5014, maintains display of thenon-underwater camera user interface without changing the camera mode.

While device is under water, performing certain functions (e.g.,adjusting the zoom level, changing the camera mode, switching betweenfront and rear facing cameras, taking a photo, as well as performingother functions) in response to detecting certain types of gestures,such as deep press gestures, reduces a likelihood of accidental userinput while device 100 is under water, thereby creating a more efficienthuman-machine interface. Further, while device 100 is not under water,the likelihood of accidental input is less than the likelihood ofaccidental input while device 100 is under water. In such environments,performing certain functions in response to detecting other types ofinputs, such as drag gestures, which require less time and effort tocomplete, increases the efficiency and rate at which inputs are entered,also creates a more efficient human-machine interface. Forbattery-operated computing devices, enabling a user to access differentfunctions of device 100 faster, more efficiently, and with less errorwhile device 100 is under water and while device 100 is not under waterconserves power and increases time between battery charges.

In some embodiments, device 100, while displaying the first userinterface, detects (718), via the one or more input devices, a firstuser input to interact with a physical button of device 100. In someembodiments, device 100, in response to detecting the first user input,performs (718) the first function. FIG. 6I, for example, illustratesdisplaying underwater camera user interface 5115 while device 100 isunder water. In some embodiments, pressing volume adjustment button 5012or 5014 while underwater camera user interface 5115 is displayed causesdevice 100 to switch between front and rear facing cameras of device100. In one or more of such embodiments, device 100, in response todetecting a press of volume adjustment button 5012 or 5014, switchesbetween front and rear facing cameras of device 100. However, where theuser optionally performs a tap gesture with contact over switch cameraaffordance 5150F of FIG. 6I while device 100 is under water, device 100maintains display of underwater camera user interface 5115 withoutswitching the cameras of device 100.

In some embodiments, device 100, in response to receiving the firstrequest, and in accordance with a determination that device 100 is notunder water, displays (718) a first user interface element that isassociated with the first function in the second user interface. In someembodiments, device 100 detects (718), via the one or more inputdevices, a second user input to select the first user interface element.In some embodiments, device 100, in accordance with a determination thatthe second user input is a touch input performed over the first userinterface element, performs (718) the first function. In someembodiments, device 100, in accordance with a determination that thesecond user input is not a touch input performed over the first userinterface element, maintains display (718) of the first user interfaceelement without performing the first function. FIG. 6A, for example,illustrates device 100 while device 100 is not under water. In someembodiments, the user optionally performs a tap gesture with contactover camera affordance 5020 of FIG. 6A, and device 100, in response todetecting the tap gesture, displays a non-underwater camera userinterface, which also contains a switch camera affordance similar toswitch camera affordance 5150F of FIG. 6I. In one or more embodiments,the user performs a tap gesture with contact over the switch cameraaffordance that is displayed in the non-underwater camera userinterface, and device 100, in response to detecting the tap gesture,switches the camera of device 100. Further, in one or more embodiments,where the non-underwater camera user interface is displayed on display112, the user optionally presses volume adjustment buttons 5012 and 5014of device 100. However, device 100, in response to detecting pressing ofvolume adjustment buttons 5012 and 5014, maintains display of thenon-underwater camera user interface without switching the camera ofdevice 100.

While device is under water, performing certain functions (e.g.,adjusting the zoom level, changing the camera mode, switching betweenfront and rear facing cameras, taking a photo, as well as performingother functions) in response to detecting certain types of gestures,such as pressing physical buttons 5012, 5014, or 5016 of device 100,reduces a likelihood of accidental user input while device 100 is underwater, thereby creating a more efficient human-machine interface.Further, while device 100 is not under water, the likelihood ofaccidental input is less than the likelihood of accidental input whiledevice 100 is under water. In such environments, performing certainfunctions in response to detecting other types of inputs, such as tapgestures, which require less time and effort to complete, increases theefficiency and rate at which inputs are entered, also creates a moreefficient human-machine interface. For battery-operated computingdevices, performing different functions of device 100 faster, moreefficiently, and with less error while device 100 is under water andwhile device 100 is not under water conserves power and increases timebetween battery charges.

In some embodiments, device 100, in response to receiving the firstrequest, and in accordance with a determination that device 100 is underwater, displays (720) a first user interface element that is associatedwith the first function in the first user interface. In someembodiments, device 100 detects (720), via the one or more inputdevices, a first user input to select the first user interface element.In some embodiments, device 100, in accordance with a determination thatthe first user input is an input with an intensity above a respectiveintensity threshold detected at a location corresponding to the firstuser interface element, performs (720) the first function. In someembodiments, device 100, in accordance with a determination that thefirst user input is an input with an intensity that is not above therespective intensity threshold detected at the location corresponding tothe first user interface element, maintains display (720) of the firstuser interface element without performing the first function. FIG. 6N,for example, illustrates displaying underwater camera user interface5115 while device 100 is under water. Further, FIGS. 6N-6O, illustratedetecting a deep press gesture with contact 5514 over take photoaffordance 5150E, and taking a photo with the rear facing camera inresponse to detecting the deep press gesture. In some embodiments, theuser optionally performs a tap gesture with contact over take photoaffordance 5150E. Device 100, in response to detecting the tap gesture,treats the tap gesture as an accidental input and maintains display ofunderwater camera user interface 5115 without taking a photo with therear facing camera.

In some embodiments, device 100, in response to receiving the firstrequest, and in accordance with a determination that device 100 is notunder water, displays (720) a second user interface element that isassociated with the first function in the second user interface. In someembodiments, device 100 detects (720), via the one or more inputdevices, a second user input to select the second user interfaceelement. In some embodiments, device 100, in accordance with adetermination that the second user input is a touch input performed overthe second user interface element, performs (720) the first function. Insome embodiments, device 100, in accordance with a determination thatthe second user input is not a touch input performed over the seconduser interface element, maintains display (720) of the second userinterface element without performing the first function.

FIG. 6A, for example, illustrates device 100 while device 100 is notunder water. In some embodiments, the user optionally performs a tapgesture with contact over camera affordance 5020 of FIG. 6A, and device100, in response to detecting the tap gesture, displays a non-underwatercamera user interface. In one or more embodiments, the user performs atap gesture with contact on a take photo affordance similar to takephoto affordance 5150E of FIG. 6O, and device 100, in response todetecting the tap gesture, takes a photo with the camera of device 100.Further, in one or more embodiments, where the non-underwater camerauser interface is displayed on display 112 while device 100 is not underwater, the user optionally performs a deep press gesture with contactover the take photo affordance. However, device 100, in response todetecting the deep press gesture, maintains display of thenon-underwater camera user interface without taking a photo with thecamera.

While device is under water, performing certain functions (e.g.,adjusting the zoom level, changing the camera mode, switching betweenfront and rear facing cameras, taking a photo, as well as otherfunctions) in response to detecting certain types of gestures, such asdeep press gestures, reduces a likelihood of accidental user input whiledevice 100 is under water, thereby creating a more efficienthuman-machine interface. Further, while device 100 is not under water,the likelihood of accidental input is less than the likelihood ofaccidental input while device 100 is under water. In such environments,performing certain functions in response to detecting other types ofinputs, such as tap gestures, which require less time and effort tocomplete, increases the efficiency and rate at which inputs are entered,also creates a more efficient human-machine interface. Forbattery-operated computing devices, performing different functions ofdevice 100 faster, more efficiently, and with less error while device100 is under water and while device 100 is not under water conservespower and increases time between battery charges.

In some embodiments, device 100, in response to receiving the firstrequest, and in accordance with a determination that device 100 is underwater, displays (722) one or more user interface elements associatedwith the first function. In some embodiments, device 100 detects (722),via the one or more input devices, a first user input to press a firstphysical button of device 100. In some embodiments, device 100, inresponse to detecting the first user input, selects (722) one of the oneor more user interface elements. FIGS. 6F-6G, for example, illustratedetecting a deep press gesture with contact 5504 over camera affordance5020, and in response to detecting the deep press gesture while device100 is under water, displaying underwater user interface 5113 on display112. Further, FIGS. 6G and 6I, for example, illustrate detecting a pressof push button 5016 with contact 5506 on push button 5016 while focus ison camera affordance 5050, and in response to detecting the press ofpush button 5016, accessing the camera application and displayingunderwater camera user interface 5115 on display 112. Allowing the userto select a user interface element such as camera affordance 5050 ofFIG. 6G by pressing a physical button, such as push button 5016 of FIG.6G provides a simple way for the user to select user interface elementsthat are displayed on display 112, thereby reducing the cognitive burdenon the user and creates a more efficient human-machine interface. Forbattery-operated computing devices, allowing the user to select userinterface elements faster and more efficiently conserves power andincreases time between battery charges.

In some embodiments, device 100, in response to receiving the firstrequest, and in accordance with a determination that device 100 is underwater, displays (724) a plurality of user interface elements associatedwith the first function. In some embodiments, device 100 detects (724),via the one or more input devices, a first user input to press a firstphysical button of device 100. In some embodiments, device 100, inresponse to detecting the first user input, selects (724) a first userinterface element of the plurality of user interface elements. In someembodiments, device 100, after selecting the first user interfaceelement, detects (724), via the one or more input devices, a second userinput to press a second physical button of device 100. In someembodiments, device 100, in response to detecting the second user input,unselects (724) the first user interface element. In some embodiments,device 100 selects (724) a second user interface element of theplurality of user interface elements. FIGS. 6F-6G, for example,illustrate detecting a deep press gesture with contact 5504 over cameraaffordance 5020, and in response to detecting the deep press gesturewhile device 100 is under water, displaying underwater camera userinterface 5115 containing camera affordance 5050, flashlight affordance5051, timer affordance 5052, alarm affordance 5053, and exit affordance5054. In some embodiments, user interface 5113 of FIG. 6G containsmultiple user interface elements associated with different camerafunctions and settings, such as, but not limited to photo mode, videomode, square mode, delay shutter, delay shutter, set flash, as well asother camera functions or settings. The user optionally presses volumeadjustment button 5012 or 5014 to switch between different userinterface elements of the camera functions and settings. For example,the user optionally presses volume adjustment button 5014, and device100, in response to detecting pressing of volume adjustment button 5014while focus is on photo mode, unselects the user interface elementassociated with photo mode, and selects the user interface elementassociated with video mode. Allowing the user to press physical buttonsto select different user interface elements that are displayed whiledevice 100 is under water provides the user with a simple method toswitch between different user interface elements, and to adjustdifferent settings or functions of device 100, thereby reducing theuser's cognitive burden and creating a more efficient human-machineinterface. For battery-operated computing devices, allowing the user toselect user interface elements faster and more efficiently conservespower and increases time between battery charges.

In some embodiments, device 100, in response to receiving the firstrequest, and in accordance with a determination that device 100 is underwater, displays (726) one or more user interface elements that areassociated with one or more functions in the first user interface. Insome embodiments, device 100, in accordance with a determination thatdevice 100 is not under water, displays (726) the second user interfacewithout displaying the one or more user interface elements, where thefirst user interface and the second user interface are wake screen userinterfaces that are displayed while device 100 is in a wake screen mode.FIG. 6C, for example illustrates displaying camera affordance 5050,flashlight affordance 5051, timer affordance 5052, alarm affordance5053, and exit affordance 5054 in underwater user interface 5113. Insome embodiments, user interface 5113 as illustrated in FIG. 6C is awake screen user interface that is displayed when device 100 first wakesup while under water. Further, FIG. 6A illustrates displaying cameraaffordance 5020 and flashlight affordance 5021 in user interface 5112without displaying a timer affordance or an alarm affordance in userinterface 5112. In some embodiments, user interface 5112 as illustratedin FIG. 6A is a wake screen user interface that is displayed when device100 first wakes up while device 100 is not under water. Displaying userinterface elements associated with functions and applications that areuseful to the user in an underwater wake screen user interface allowsthe user to easily access different functions and applications of device100 while device 100 is under water, thereby reducing the cognitiveburden on the user. Further, not displaying certain user interfaceelements (such as user interface elements that are associated withcertain functions and applications that are not often accessed by theuser) in a non-underwater wake screen user interface when device 100wakes up while not being under water reduces the number of extraneoususer interface elements that are displayed in the wake screen userinterface, thereby also reducing the cognitive burden on the user andcreating a more efficient human-machine interface. For battery-operatedcomputing devices, providing the user with access to user interfaceelements associated with functions and applications the user will likelyuse, and allowing the user to select user interface elements faster, andmore efficiently, conserves power and increases time between batterycharges.

In some embodiments, the one or more user interface elements areassociated with applications selected from a group consisting of a timerapplication, an alarm application, and a flashlight application (728).FIG. 6C, for example, illustrates displaying camera affordance 5050,flashlight affordance 5051, timer affordance 5052, and alarm affordance5053 in underwater user interface 5113. Providing user interfaceelements of different applications and functions accessible to the userwhile device 100 is under water in a common user interface allows theuser to quickly access different applications and functions accessibleto the user while device 100 is under water, thereby reducing thecognitive burden on the user and creating a more efficient human-machineinterface. For battery-operated computing devices, allowing the user toselect user interface elements faster and more efficiently conservespower and increases time between battery charges.

In some embodiments, device 100, in response to receiving the firstrequest, and in accordance with a determination that device 100 is underwater, displays (730) a camera user interface element in the first userinterface. In some embodiments, device 100 detects (730), via the one ormore input devices, a first user input to select the camera userinterface element to access a camera of device 100. In some embodiments,device 100, in response to detecting the first user input, displays(730) an underwater camera user interface having one or more camera userinterface elements that are associated with camera settings of thecamera, where the user interacts with one or more of the one or morecamera user interface elements to adjust one or more correspondingcamera settings of the camera. In some embodiments, device 100 detects(730), via the one or more input devices, a second user input to selecta first camera user interface element of the one or more camera userinterface elements. In some embodiments, device 100, in response todetecting the second user input, adjusts (730) a corresponding camerasetting associated with the first camera user interface element. FIGS.6G and 6I, for example, illustrate detecting a press of push button 5016with contact 5506 on push button 5016 while focus is on cameraaffordance 5050, and in response to detecting the press while device 100is under water, displaying underwater camera user interface 5115 ondisplay 112. In the illustrated embodiment of FIG. 6I, take photoaffordance 5150E is one of several user interface elements associatedwith different camera settings of the camera. Further, FIGS. 6N-6Oillustrates detecting a deep press gesture with contact 5514 over takephoto affordance 5150E, and in response to the deep press gesture,taking a photo with the camera. The user optionally performs a deeppress gesture with contact over video mode affordance 5150A, which is auser interface element that is associated with another camera setting.Device 100, in response to detecting the deep press gesture, switchesthe camera mode from photo mode to video mode. Similarly, the useroptionally performs a deep press gesture with contact over timeraffordance 5150H, which is another user interface element that isassociated with another camera setting. Device 100, in response todetecting the deep press gesture, adjust the shutter delay of thecamera. Displaying user interface elements associated with differentcamera settings in a camera user interface provides the user access tomultiple camera setting and allows the user to make adjustments todifferent camera settings from a common user interface, thereby reducingthe cognitive burden on the user and creating a more efficienthuman-machine interface. For battery-operated computing devices,allowing the user to access and adjust different camera settings fasterand more efficiently conserves power and increases time between batterycharges.

In some embodiments, device 100, in accordance with a determination thatdevice 100 is under water, automatically adjusts (732) one or moresettings of device 100 for underwater usage. FIGS. 6I-6O, for example,illustrate displaying underwater camera user interface 5115 in responseto detecting a user input to access the camera of device 100. In someembodiments, device 100, after determining that it is under water,automatically adjusts certain camera settings to improve performance ofthe camera while used under water. For example, device 100 automaticallyadjusts the default shutter speed and flash setting of the camera whiledevice 100 is under water to improve the quality of photos taken whiledevice 100 is under water. Automatically adjusting one or more settingsof device 100 while device 100 is under water improves performance ofdevice 100 without requiring user input, thereby reducing the cognitiveburden of the user and creating a more efficient human-machineinterface. For battery-operated computing devices, improving theperformance of device 100 while device 100 is under water conservespower and increases time between battery charges.

In some embodiments, device 100, in accordance with a determination thatdevice 100 is under water, activates (734) a lost phone mode. In someembodiments, while device 100 is in the lost phone mode, device 100periodically emits (734) a flash from device 100. FIG. 6C, for example,illustrates device 100 being under water. In some embodiments, device100 activates a lost phone mode after determining that it is underwater. In one or more of such embodiments, device 100 activates the lostphone mode after determining that it is under water and after device 100has not detected a user input for a threshold period of time. In one ormore of the foregoing embodiments, device 100, after activating a lostphone mode, also emits flashes to provide a visual indication of thecurrent location of device 100. Providing an easily recognizable visualindication of the current location of device 100 helps the user, as wellas other individuals, locate device 100 while device 100 is under water,thereby reducing the cognitive burden of the user and creating a moreefficient human-machine interface. For battery-operated computingdevices, allowing the user or other individuals to determine the currentlocation of device 100, and thereby recover device 100 faster and moreefficiently, conserves power expanded by device 100 while device 100 islost under water and increases time between battery charges.

In some embodiments, while device 100 is in the lost phone mode, device100 periodically emits (736) a strobe pattern from device 100.Continuing with the foregoing example, where device 100 activates thelost phone mode after determining that it is under water, in someembodiments, device 100 also emits a strobe pattern, which allows theuser or other individuals to identify the current location of device100. Providing an easily recognizable visual indication of the currentlocation of device 100 helps the user, as well as other individuals,locate device 100 while device 100 is under water, thereby reducing thecognitive burden of the user and creating a more efficient human-machineinterface. For battery-operated computing devices, allowing the user orother individuals to determine the current location of device 100, andthereby recover device 100 faster and more efficiently, conserves powerexpanded by device 100 while device 100 is lost under water andincreases time between battery charges.

In some embodiments, while device 100 is in the lost phone mode, device100 receives (738) a communication from a second electronic device. Insome embodiments, device 100, in response to receiving the communicationfrom the second electronic device, activates (738) the display of device100. FIG. 6C, for example, displays underwater user interface 5113 whiledevice 100 is under water. In some embodiments, device 100 subsequentlyenters into a sleep mode after a period of inactivity, where display 112is turned off during sleep mode. Further, device 100, while in the sleepmode, receives a communication from another electronic device, and inresponse to receiving the communication, activates display 112 to notifythe user about the communication. In one or more of such embodiments,device 100 also displays an indication of the communication on display100. For example, where the communication is a text message from theelectronic device of the user's wife, device 100 also overlays userinterface 5113 with a message bubble containing the text message.Activating display 112 after receiving a communication from anotherelectronic device allows the user to become cognizant of an incomecommunication from another electronic device, thereby reducing thecognitive burden on the user and creating a more efficient human-machineinterface. For battery-operated computing devices, allowing the user todetermine the presence of an incoming communication faster and moreefficiently conserves power and increases time between battery charges.

In some embodiments, while device 100 is in the lost phone mode, device100 receives (740) a communication from a second electronic device. Insome embodiments, device 100, in response to receiving the communicationfrom the second electronic device, determines (740) a position of device100 relative to the second electronic device. In some embodiments,device 100 transmits (740) a request to the second electronic device todisplay the position of device 100 relative to the second electronicdevice on a display of the second electronic device. FIG. 6C, forexample, displays underwater user interface 5113 while device 100 isunder water. In some embodiments, device 100, after receiving acommunication from another electronic device (e.g., another electronicdevice of the user, an electronic device of the user's spouse, anelectronic device of a nearby user, an electronic device of a search andrescue personnel, etc.), also determines a current location of device100 and a location of device 100 with respective to the other device,and provides the current location of device 100 and the relativelocation of device 100 with respect to the other device to the otherelectronic device with a request to display the current location on theother electronic device. Providing the current location of device 100and a relative location of device 100 with respect to another electronicdevice to the other electronic device allows the user of the otherelectronic device to quickly locate device 100, and in certaincircumstances, retrieve device 100 and possibly rescue the user fromunder water. In some embodiments, device 100 automatically provides thelocation of device 100 without requiring any input from the user,thereby reducing the cognitive burden on the user and creating a moreefficient human-machine interface. For battery-operated computingdevices, allowing the user of another electronic device to determine thecurrent location of device 100, and thereby recover device 100 fasterand more efficiently conserves power expanded by device 100 while device100 is under water, and increases time between battery charges.

In some embodiments, device 100, in accordance with a determination thatdevice 100 is under water, displays (742) a request for userconfirmation that device 100 is under water. In some embodiments, device100 detects (742), via the one or more input devices, a first user inputto confirm that device 100 is under water. In some embodiments, device100, in response to detecting the first user input, displays (742) thefirst user interface on the display. FIG. 6C, for example, illustratesdevice 100 determining that it is under water, and automaticallydisplaying underwater user interface 5113. In some embodiments, afterdevice 100 has determined that it is under water, device 100 queries theuser to confirm that device 100 is under water. In one or more of suchembodiments, device 100 displays underwater user interface 5113 afterdetecting a user input confirming that device 100 is under water.Providing the user an option to confirm that device 100 is under waterbefore displaying an underwater user interface reduces the likelihoodthat device 100 incorrectly determines that it is under water. Further,providing the user with an option to confirm that device 100 is underwater also allows the user to determine whether the user would like tointeract with underwater user interfaces. The foregoing reduces thecognitive burden on the user and creates a more efficient human-machineinterface. For battery-operated computing devices, accuratelydetermining whether device 100 is under water conserves power andincreases time between battery charges.

In some embodiments, device 100, while displaying the first userinterface, determines (744) whether device 100 is no longer under water.In some embodiments, device 100 automatically removes (744) the displayof the first user interface after a determination that device 100 is nolonger under water. FIG. 6V, for example, illustrates device 100determining that it is no longer under water, and in response to thedetermination, automatically removing underwater user interface 5113.Automatically removing an underwater user interface when device 100 isno longer under water, and optionally, displaying a correspondingnon-underwater user interface without any user input reduces thecognitive burden on the user and creates a more efficient human-machineinterface. For battery-operated computing devices, removing underwateruser interfaces faster and more efficiently after device 100 is nolonger under water, and optionally, automatically displayingcorresponding non-underwater user interfaces faster and moreefficiently, conserves power and increases time between battery charges.

In some embodiments, device 100 determines (746) that device 100 isunder water if a first threshold amount of the display of device 100 iswet. In some embodiments, device 100 determines that device 100 is notunder water if a second threshold amount of the display of device 100 iswet, where the first amount percentage is greater than the secondthreshold amount. FIG. 6C, for example illustrates device 100determining that it is under water after approximately 75% of display112 is wet. FIG. 6V, for example, illustrates device 100 determiningthat it is not under water after approximately 25% of display is wet.Setting different thresholds to determine whether device 100 is underwater or no longer under water allows device to designate differentcriteria for determining whether device 100 is under water or not underwater. Further, automatically determining whether device 100 is underwater or not under water without user input reduces the cognitive burdenon the user and creates a more efficient human-machine interface. Forbattery-operated computing devices, automatically determining whetherdevice 100 is under water or not under water faster, more accurately,and more efficiently conserves power and increases time between batterycharges.

In some embodiments, device 100, while displaying the first userinterface, determines (748) whether device 100 is no longer under waterfor a threshold period of time. In some embodiments, device 100automatically removes (748) the display of the first user interfaceafter a determination that device 100 is no longer under water for thethreshold period of time. FIGS. 6U-6V, for example, illustrates device100 determining that a threshold percentage of display 112 is no longerwet, and in response to determining that the threshold percentage ofdisplay 112 is no longer wet, removing display of underwater userinterface 5113. In some embodiments, device 100 removes the display ofan underwater user interface after device 100 determines that it is nolonger under water for a threshold period of time. Removing display ofan underwater user interface after device 100 is no longer under waterfor a threshold period of time increases the likelihood that device 100is no longer under water when the display of the underwater userinterface is removed. Further, automatically removing the underwateruser interface without requiring additional user inputs reduces thecognitive burden on the user and creates a more efficient human-machineinterface. For battery operated computer devices, determining thatdevice 100 is no longer under water faster and more efficiently, andautomatically removing a previously displayed underwater user interfacewithout user inputs conserve power and increase time between batterycharges.

In some embodiments, device 100, in accordance with a determination thatdevice 100 is under water, displays (750) an underwater indicator on thedisplay. In some embodiments, device 100, in accordance with adetermination that device 100 is no longer under water, removes (750)the underwater indicator from the display. FIG. 6C, for exampleillustrates displaying underwater indicator 5018 in the status barregion of display 112 in response to determining that device 100 isunder water. Further, FIG. 6V illustrates removing underwater indicator5018 of FIG. 6C from display after determining that device 100 is nolonger under water. Displaying an underwater indicator, such asunderwater indicator 5018 of FIG. 6C on display after device 100 andremoving the underwater indicator from display after device 100 is nolonger under water allow the user to quickly determine whether device100 is under water or not under water. The foregoing reduces thecognitive burden on the user and creates a more efficient human-machineinterface. For battery-operated computing devices, allowing a user todetermine whether device 100 is under water or not under water fasterand more efficiently conserves power and increases time between batterycharges.

In some embodiments, while the underwater indicator is displayed in thefirst user interface, device 100 detects (752), via the one or moreinput devices, a first user input to remove the first user interface. Insome embodiments, device 100, in response to detecting the first userinput, removes (752) the first user interface from the display. FIGS.6Q-6R, for example illustrates detecting a press of push button 5016with contact 5520 on push button 5016, and in response to detecting thepress of push button 5016 while underwater indicator 5018 is displayedon display 112, removing underwater user interface 5113 for display 112.Allowing the user to enter certain inputs to remove display of a userinterface provides the user with a simple way of controlling which userinterfaces are displayed on display 112, thereby reducing the cognitiveburden on the user and creating a more efficient human-machineinterface. For battery-operated computing devices, removing display ofuser interfaces faster and more efficiently conserves power andincreases time between battery charges.

In some embodiments, device 100, in response to a determination thatdevice 100 is under water, deactivates (754) one or more modules ofdevice 100. FIGS. 6C-6U, for example, illustrate device 100 while device100 is under water. In some embodiments, device 100, after determiningthat it is under water, deactivates certain modules that are notaccessible by the user or are infrequently used by the user while device100 is under water. For example, device 100 after determining that it isunder water, deactivates touch modules, telephone modules, and acousticmodules. In one or more embodiments, device 100 automaticallydeactivates the modules without user input, thereby reducing thecognitive burden on the user and creating a more efficient human-machineinterface. For battery-operated computing devices, deactivating certainmodules not accessible or not frequently used by the user faster, moreefficiently, and without user input, conserves power and increases timebetween battery charges.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the techniques and their practical applications. Othersskilled in the art are thereby enabled to best utilize the techniquesand various embodiments with various modifications as are suited to theparticular use contemplated.

Although the disclosure and examples have been fully described withreference to the accompanying drawings, it is to be noted that variouschanges and modifications will become apparent to those skilled in theart. Such changes and modifications are to be understood as beingincluded within the scope of the disclosure and examples as defined bythe claims.

As described above, one aspect of the present technology is thegathering and use of data available from various sources to improve thedelivery to users of invitational content or any other content that maybe of interest to them. The present disclosure contemplates that in someinstances, this gathered data may include personal information data thatuniquely identifies or can be used to contact or locate a specificperson. Such personal information data can include demographic data,location-based data, telephone numbers, email addresses, home addresses,or any other identifying information.

The present disclosure recognizes that the use of such personalinformation data, in the present technology, can be used to the benefitof users. For example, the personal information data can be used todeliver targeted content that is of greater interest to the user.Accordingly, use of such personal information data enables calculatedcontrol of the delivered content. Further, other uses for personalinformation data that benefit the user are also contemplated by thepresent disclosure.

The present disclosure further contemplates that the entitiesresponsible for the collection, analysis, disclosure, transfer, storage,or other use of such personal information data will comply withwell-established privacy policies and/or privacy practices. Inparticular, such entities should implement and consistently use privacypolicies and practices that are generally recognized as meeting orexceeding industry or governmental requirements for maintaining personalinformation data private and secure. For example, personal informationfrom users should be collected for legitimate and reasonable uses of theentity and not shared or sold outside of those legitimate uses. Further,such collection should occur only after receiving the informed consentof the users. Additionally, such entities would take any needed stepsfor safeguarding and securing access to such personal information dataand ensuring that others with access to the personal information dataadhere to their privacy policies and procedures. Further, such entitiescan subject themselves to evaluation by third parties to certify theiradherence to widely accepted privacy policies and practices.

Despite the foregoing, the present disclosure also contemplatesembodiments in which users selectively block the use of, or access to,personal information data. That is, the present disclosure contemplatesthat hardware and/or software elements can be provided to prevent orblock access to such personal information data. For example, in the caseof advertisement delivery services, the present technology can beconfigured to allow users to select to “opt in” or “opt out” ofparticipation in the collection of personal information data duringregistration for services. In another example, users can select not toprovide location information for targeted content delivery services. Inyet another example, users can select to not provide precise locationinformation, but permit the transfer of location zone information.

Therefore, although the present disclosure broadly covers use ofpersonal information data to implement one or more various disclosedembodiments, the present disclosure also contemplates that the variousembodiments can also be implemented without the need for accessing suchpersonal information data. That is, the various embodiments of thepresent technology are not rendered inoperable due to the lack of all ora portion of such personal information data. For example, content can beselected and delivered to users by inferring preferences based onnon-personal information data or a bare minimum amount of personalinformation, such as the content being requested by the deviceassociated with a user, other non-personal information available to thecontent delivery services, or publicly available information.

What is claimed is:
 1. A method comprising: at an electronic device incommunication with a display device and one or more input devices:displaying, via the display device, a first user interface, wherein: inaccordance with a determination that the electronic device isunderwater, the first user interface includes a first set of one or moreaffordances that are selectable to access one or more first functions ofthe electronic device; and in accordance with a determination that theelectronic device is not underwater, the first user interface includes asecond set of one or more affordances, different from the first set ofone or more affordances, that are selectable to access one or moresecond functions of the electronic device; while displaying the firstuser interface, receiving, via the one or more input devices, a firstinput corresponding to selection of a first respective affordance in thefirst user interface; and in response to receiving the first input,performing a first respective function associated with the firstrespective affordance.
 2. The method of claim 1, wherein the first setof one or more affordances includes the second set of one or moreaffordances, and the second set of one or more affordances does notinclude at least one affordance in the first set of one or moreaffordances.
 3. The method of claim 1, wherein the first user interfaceis a wake screen user interface of the electronic device.
 4. The methodof claim 1, wherein the first set of one or more affordances isdisplayed according to a first arrangement on the first user interface,and the second set of one or more affordances is displayed according toa second arrangement, different from the first arrangement, on the firstuser interface.
 5. The method of claim 1, wherein the first set of oneor more affordances includes a first affordance that is selectable toaccess a first function, and the second set of one or more affordancesincludes a second affordance that is selectable to access the firstfunction.
 6. The method of claim 5, wherein the first affordance has afirst visual appearance, and the second affordance has a second visualappearance, different from the first visual appearance.
 7. The method ofclaim 1, wherein the one or more first functions include a respectivefunction of a first respective application installed on the electronicdevice.
 8. The method of claim 7, wherein the one or more secondfunctions include a respective function of a second respectiveapplication installed on the electronic device.
 9. The method of claim1, wherein the electronic device displays the first user interface inresponse to waking up while the electronic device is underwater.
 10. Themethod of claim 1, wherein the electronic device displays the first userinterface in response to waking up while the electronic device is notunderwater.
 11. A non-transitory computer-readable storage mediumincluding instructions, which when executed by one or more processors ofan electronic device, cause the electronic device to perform a methodcomprising: displaying, via a display device, a first user interface,wherein: in accordance with a determination that the electronic deviceis underwater, the first user interface includes a first set of one ormore affordances that are selectable to access one or more firstfunctions of the electronic device; and in accordance with adetermination that the electronic device is not underwater, the firstuser interface includes a second set of one or more affordances,different from the first set of one or more affordances, that areselectable to access one or more second functions of the electronicdevice; while displaying the first user interface, receiving, via one ormore input devices, a first input corresponding to selection of a firstrespective affordance in the first user interface; and in response toreceiving the first input, performing a first respective functionassociated with the first respective affordance.
 12. An electronicdevice comprising: one or more processors; and memory storinginstructions, which when executed by the one or more processors, causethe electronic device to perform a method comprising: displaying, via adisplay device, a first user interface, wherein: in accordance with adetermination that the electronic device is underwater, the first userinterface includes a first set of one or more affordances that areselectable to access one or more first functions of the electronicdevice; and in accordance with a determination that the electronicdevice is not underwater, the first user interface includes a second setof one or more affordances, different from the first set of one or moreaffordances, that are selectable to access one or more second functionsof the electronic device; while displaying the first user interface,receiving, via one or more input devices, a first input corresponding toselection of a first respective affordance in the first user interface;and in response to receiving the first input, performing a firstrespective function associated with the first respective affordance.